Account Settings

Manage users, teams, roles, and API access credentials.

Control who can access the platform and what they can do. Manage users, organize them into teams, and issue API keys for programmatic access.

Manage access

Assign roles to people and group them into teams for product-space access.

Secure integrations

Create permission-scoped API keys for the integrations that need them.

At a glance

Area	Use it to	Start here
Users	Invite people and assign roles	Users
Teams	Group members and grant agent permissions	Teams
API Keys	Create programmatic credentials	API Keys

People receive roles scoped to product spaces. Teams group people together. Integrations receive API keys with selected permissions.

Roles and spaces

Access in Qore is organized around two ideas that recur throughout this module:

• Spaces are the product surfaces a role or team applies to: Studio (building), Console, and Control Center (this surface).

• Roles grant permissions within a space. The available roles span all three spaces plus account-wide scopes: Studio Collaborator, Studio Builder, Studio Admin, Console Admin, Control Center Admin, Control Center Auditor, Account Admin, and System Admin. A single user can hold several roles at once.

Users

The Users screen lists everyone with access to the account. Open Account Settings → Users.

The Users screen, listing everyone with access to the account.

Search by name or email, narrow by status, and use + Create User to add someone. Each row shows the user's Name, Email, Phone, and Status — Invited (added but not yet active) or Active — with a per-row Actions menu.

Create or edit a user

Creating or editing a user opens a dialog with the same fields:

• First Name and Last Name — required.

• Email — required. Where the invitation is sent and how the user signs in.

• Phone Number — optional, with a country code.

• Role — required. One or more roles from the list in Roles and spaces. This is what determines what the user can do.

Assigning one or more roles when creating or editing a user.

Creating a user sends a real invitation, and changing a role changes what that person can access. Set roles deliberately.

Teams

Teams group members together, scope them to spaces, and grant role-based permissions on specific agents. Open Account Settings → Teams. Each team is listed with its Team name, its Spaces, its Members count, and a per-row Actions menu. Teams are also what Human Review assignments flow through.

Create a team

+ Create Team opens a two-step dialog.

1

Step 1: Set up the team

• Team name — a label for the team (for example, Lending Ops).

• Spaces — which products the team operates in: Studio, Console, or Control Center.

• Members — add people from the account and set each member's role; you can change these later. Invite someone new adds a person who isn't yet on the account.

Click Continue to move to Step 2.

2

Step 2: Grant agent permissions

Grant the team role-based permissions on specific agents.

Step 1 of creating a team — name, spaces, and members.

API Keys

API Keys are credentials for programmatic access to the platform. Open Account Settings → API Keys. Search by name or key ID, and use + Create API Key to issue one.

Create an API key

+ Create API Key opens a dialog:

• Key name — a label for the key (for example, Reporting integration).

• Select Permissions — required. A searchable checklist of the permissions to grant — for example, Create Account, Manage Accounts, Create User, View Users, Define Roles, Manage Brands, and Create Workspace. Grant a key only the permissions it needs.

Click Create Key to issue it. The button stays disabled until the key has a name and at least one permission.

Creating an API key with a scoped set of permissions.

An API key is a credential that can carry account-management permissions, such as creating users or defining roles. Scope each key to the minimum it needs, and store the key value securely — it grants whatever access you selected.

Notes

• Roles are cross-cutting: a user can hold several at once, and roles are scoped to the Studio, Console, and Control Center spaces plus account-wide.

• Team creation is a two-step flow; the second step grants per-agent permissions, so a team isn't fully configured until both steps are complete.

• API-key permissions are granular and can be account-wide — review the selected permissions before issuing a key.

Related

Control CenterEvaluation & QualityControls & AuditCredits & Tokens