Skip to main content
Version: 3.6.1-rc.2

Quickstart: manage your tenant

This quickstart is for tenant administrators: people with the Owner role in a tenant. In about 10 minutes you invite someone, put them in a group, give the group access to a resource, and check what the tenant uses.

A tenant administrator manages one tenant. Platform administrators manage the platform as a whole: all tenants, model deployments and platform-wide usage. See Administer the Platform.

To get started, you need:

  • the Owner role in the tenant.
  • a resource you created in the tenant to share, such as a RAG endpoint, a preset agent, an MCP server or a connected external model.

1. Invite a member​

  1. Select Members in the tenant sidebar, then Invite member.
  2. Enter their Email address and choose a Role. Member is enough to use what you share with them.
  3. Select Send invitation.

The invitation stays under Pending invites until they accept it the next time they sign in. See Manage members and roles for what each role can do.

2. Create a group and add the member​

  1. On the Members page, select the Groups tab, then Create group.
  2. Enter a Group name, such as Engineering, and select Create group.
  3. Open the group, select Add, pick the member and select Add members.

Only members can join a group, so the person must accept your invitation first. If it's still pending, come back to this step later.

To delete a group or remove members, see Groups.

3. Share a resource with the group​

  1. Open the resource, for example RAG → Endpoints, select the endpoint you created, then its Users tab.
  2. Under Users, select Add user, search for the group and select Add.

Everyone in the group can now use the resource, including people you add to the group later. To let the group or a user manage the resource as well, use Add administrator instead.

4. Check the tenant's usage​

Select Usage in the tenant sidebar. It shows the tokens your tenant used over time and the models it used most. Select Export API-key CSV to download the usage per API key.

Next steps​