Managing your organization
This guide covers how to manage your organization's profile, team members, roles, and security settings in Compliance Studio. Organization management is available to users with the Owner or Admin role. If you have a different role, contact your organization's Owner or Admin to request changes.
Organization profile
Your organization profile defines how your organization is displayed within Compliance Studio.
Organization name and logo
Update your organization's display name and upload a logo through the organization settings. The logo is displayed in the sidebar and in any shared contexts within Compliance Studio.
Verified domains
Verified domains control how new members can join your organization. After adding a domain, you can choose between:
- No automatic enrollment -- Members can only join through a direct invitation
- Automatic suggestions -- Users with a matching email domain receive a suggestion to request access, but must still be approved by an administrator
Verified domains also play an important role in SSO configuration, as they determine which users are redirected to your identity provider during login.
Team members
Viewing the member list
The member list displays all current members of your organization along with their names, email addresses, and assigned roles. Use the search bar to find specific members.
The members view includes three tabs:
- Members -- Current active members
- Invitations -- Pending invitations that haven't been accepted yet
- Requests -- Pending join requests from users with matching verified domains
Inviting new members
- Navigate to the organization settings and select Members
- Click the Invite button
- Enter one or more email addresses, separated by commas or spaces
- Select a role from the dropdown
- Click Send invitations
Invited members are shown as (Pending) in the member list until they accept the invitation. You can resend or delete pending invitations from the Invitations tab.
Roles and permissions
Each member is assigned a role that determines what they can access and modify within Compliance Studio.
Choosing a role
| Role | Who it's for | In short |
|---|---|---|
| Owner | The account holder | Manages members, billing, policies, and every product, like an Admin. |
| Admin | People who run the account | Manages members, billing, policies, and every product. |
| Member | Compliance, product, and legal teams | Configures and publishes every product. Can't manage members, billing, or policies. |
| Developer | Engineers integrating k-ID | Configures and publishes only the products assigned to them. |
| Viewer | Stakeholders who need visibility | Reads every product and policy. Can't change anything or see API keys. |
| Product Evaluation | Teams trialing Compliance Studio | Works with every product like a Member, but can't open policies or the member list. |
| Customer Support | Player and parent support teams | Searches the event log. Can't see products. |
| Knowledge | Regulatory research | Uses KnowledgeKit only. Can't see products. |
What each role can do
| Capability | Owner | Admin | Member | Developer | Viewer | Product Evaluation |
|---|---|---|---|---|---|---|
| View products | All | All | All | Assigned | All | All |
| Create and copy products | Yes | Yes | Yes | Yes | No | Yes |
| Edit products | Yes | Yes | Yes | Assigned | No | Yes |
| View and manage API keys, webhooks, and target origins | Yes | Yes | Yes | Assigned | No | Yes |
| Push to test, submit for review, and push to live | Yes | Yes | Yes | Assigned | No | Yes |
| Read version history and diffs | Yes | Yes | Yes | Assigned | Yes | Yes |
| Reset the working copy to a published version² | Yes | Yes | Yes | Assigned | No | Yes |
| Rename a published version² | Yes | Yes | No | No | No | No |
| View policies¹ | Yes | Yes | Yes | No | Yes | No |
| Create, edit, and push policies¹ | Yes | Yes | No | No | No | No |
| Search the event log¹ | Yes | Yes | No | No | No | No |
| Manage MCP access and MCP API keys¹ | Yes | Yes | No | No | No | No |
| Upload pre-verified parents¹ | Yes | Yes | No | No | No | No |
| Manage billing and organization defaults¹ | Yes | Yes | No | No | No | No |
| View the member list | Yes | Yes | Yes | Yes | No | No |
| Invite and remove members, and change roles | Yes | Yes | No | No | No | No |
| Manage verified domains | Yes | Yes | No | No | No | No |
| Assign products to Developers | Yes | Yes | No | No | No | No |
¹ Available only when it's enabled for your organization.
² Available only when your plan includes version management.
"Assigned" means only the products an Owner or Admin has assigned to that Developer. A Developer with no assigned products sees none. A product a Developer creates or copies is assigned to them automatically.
Customer Support can search the event log¹ and view the member list. Knowledge can use KnowledgeKit and view the member list. Neither role can see products or policies.
Every role can use KnowledgeKit when your organization has it. If your plan includes KnowledgeKit seats, a member also needs a seat.
Changing a member's role
- Locate the member in the member list
- Click the dropdown next to their current role
- Select the new role
Role changes take effect immediately.
Product-level access for Developers
Members with the Developer role can be restricted to specific products within your organization, rather than having access to all products. This provides fine-grained access control when different developers work on different products.
To assign product access:
- Navigate to Member Access in the organization settings
- Find the Developer whose access you want to configure
- Click Select Products and choose the products they should have access to
Tip
Only the Developer role supports product-level access restrictions. Every other role that can see products sees all of your organization's products.
Leaving an organization
Any member can leave an organization through the organization settings. Click Leave organization and confirm your decision.
Warning
Leaving an organization immediately removes your access to all of its resources. This action can't be undone -- you'll need a new invitation to rejoin.
Owners must transfer ownership to another member before they can leave. Every organization must have at least one Owner.
Configuring SSO
Single Sign-On (SSO) lets your organization members authenticate using their existing corporate identity credentials. k-ID supports SAML 2.0 and EASIE protocols.
Single Sign-On setup is managed by k-ID support. Below is a summary of the process.
Setup process
- Contact k-ID support -- Reach out to your account representative or k-ID support to initiate SSO setup
- Configure your Identity Provider -- Using the details provided by k-ID (ACS URL, Entity ID, and metadata URL), create a k-ID application in your IdP (Okta, Azure AD, Google Workspace, OneLogin, and others)
- Exchange metadata -- Share your IdP's metadata URL or XML file with your k-ID representative
- Test the connection -- k-ID configures and tests the SSO connection on their end
- Enable SSO -- Once verified, SSO is activated for your organization
Impact of enabling SSO
Once SSO is enabled, members with email addresses matching your verified domains can no longer log in with their k-ID password. All authentication is handled through your identity provider.
Troubleshooting
If members experience issues logging in after SSO is enabled:
- Verify the user is assigned to the k-ID app in your identity provider
- Confirm the user's email domain matches a verified domain in k-ID
- Check that attribute mappings (
email,first name, andlast name) are configured correctly in your IdP - Review your identity provider's logs for authentication errors
- Contact k-ID support for further assistance
Provisioning users with SCIM
SCIM (System for Cross-domain Identity Management) lets your identity provider create, update, and deactivate Compliance Studio accounts automatically. When you assign someone to the k-ID app in your IdP, their account is created before their first login. When you unassign or deactivate them, their access is removed without waiting for them to log in again.
k-ID supports SCIM 2.0 provisioning from Okta, Microsoft Entra ID (Azure AD), and other identity providers that support SCIM 2.0. Google Workspace is also supported, but it syncs through Google's directory API instead of SCIM.
SSO is required
SCIM provisioning works alongside SSO. Your organization needs a working SSO connection before SCIM can be enabled.
Enabling SCIM
SCIM setup is managed by k-ID support, in the same way as SSO.
- Contact k-ID support -- Ask your account representative or k-ID support to enable SCIM provisioning on your SSO connection
- Receive your SCIM credentials -- k-ID provides a SCIM base URL and a bearer token. Treat the token like a password and store it only in your IdP
- Configure provisioning in your IdP -- In the k-ID application you created for SSO, turn on SCIM provisioning and enter the base URL and token. Enable the provisioning actions you want, such as creating users, updating user attributes, and deactivating users
- Push groups (optional) -- To assign roles from IdP groups, enable group push in your IdP and push the groups you want to use
- Assign users -- Assign users or groups to the k-ID app. Your IdP sends them to k-ID on its next provisioning cycle
For Google Workspace, k-ID support connects to your directory directly, so you don't need to enter a SCIM URL or token.
Required attributes
Every provisioned user must have an email address in the SCIM emails attribute. Users without one aren't provisioned. k-ID also syncs userName, name.givenName, name.familyName, and active.
Attributes that come from your IdP are read-only in Compliance Studio. To change a provisioned user's name or email, update it in your IdP.
Assigning roles from IdP groups
k-ID can map IdP groups to Compliance Studio roles. After your groups have synced at least once, tell k-ID support which group maps to which role. For example, you can map an Engineering group to Developer and an IT Admins group to Admin.
- If a user is in more than one mapped group, k-ID applies the mapping with the highest priority. Agree on the priority order with k-ID support when you set up the mappings
- Users who aren't in any mapped group get your organization's default role
- Only direct group membership counts. Nested groups aren't supported, so add users to mapped groups directly
- A role set by a group mapping can't be changed in Compliance Studio. Change the user's groups in your IdP instead
SCIM doesn't set product-level access for Developers. Assign products to Developers in Compliance Studio as usual.
Deprovisioning
When you unassign or deactivate a user in your IdP, k-ID deactivates their account and signs them out of all active sessions on the next provisioning cycle. Depending on your IdP, this can take several minutes.
Members who joined through an invitation rather than through SCIM aren't affected by SCIM changes. Remove them from the member list manually if they no longer need access.
Troubleshooting provisioning
If a user isn't provisioned or doesn't get the expected role:
- Check your IdP's provisioning logs for failed requests
- Confirm the user has an email address in the
emailsattribute - Confirm the user is a direct member of a mapped group, not a member through a nested group
- Check that your IdP is pushing groups
- Contact k-ID support for further assistance