Skip to main content
Workspace settings holds what belongs to the whole workspace rather than to one project. Brand, competitors, segments and engines are set per project, in Project settings. The screen has these sections, in this order:

​
General

Your workspace’s name and country. If your company’s name was mistyped at sign-up, correct it here.

​
Members and roles

The members list shows each person, their role and when they were last active.

​
Inviting a colleague

1

Open Members

In Workspace settings, go to Members and the invite form below the list.
2

Choose a role

Type their email address and choose admin, editor or viewer.
3

Send the invitation

Press Invite. We email them a link to join, which works for seven days. They appear in the list as pending until they accept.
An invitation never makes someone an owner. Once they have joined, an owner can change their role. A client login is invited from that client’s Reports screen instead, because it belongs to one project. Remove takes a member out of the workspace, and Cancel invite withdraws an invitation that has not been accepted. Removing someone also ends any app they connected to the workspace.

​
API keys

A key lets your own scripts and tools read this workspace through the API or the MCP server. Only owners and admins can create keys or see the list.

​
Creating a key

  1. Give it a name after where it will live, so you know which one to revoke later.
  2. Choose what it may read. Every read scope is ticked to start with.
  3. Choose what it may change. These are off unless you tick them. Write access lets a script add, re-word and archive prompts and change competitors, aliases, segments and engines. A key with write access acts as you, with your role.
  4. Optionally, set an expiry date and, if the workspace has more than one project, the projects it may reach. Leave every project unticked for all of them.
  5. Press Create key.
The whole key is shown once and never again. Copy it into your secret store straight away. If it is lost, revoke it and create another.
Each key’s row shows its scopes, the projects it can reach, its rate limit in requests a minute, its expiry and who made it, plus when it was created and last used.

​
Revoking a key

Press Revoke, then Revoke key. Anything using it stops working at once, and this cannot be undone. A revoked key stays in the list, greyed out with the time it was revoked, so you can still answer questions about it later. Authentication and scopes lists every scope and what it opens.

​
MCP endpoint

The address Claude, ChatGPT and other AI tools use to read this workspace: https://app.citino.ai/api/mcp. It is read-only.
  • In claude.ai, Claude Desktop or ChatGPT, add the address as a connector and sign in. No key needed.
  • In Claude Code, add it and run /mcp to sign in. The screen gives the command to copy.
  • A tool that sends a header instead of signing in, such as Cursor, needs an API key. Owners and admins see the setup for it here.
The MCP tab has a page for each tool.

​
Connected apps

Every app that someone signed in to this workspace with Citino: the app, who connected it (owners and admins only), when, and when it was last used. Each app reads what the person who connected it can read, and never changes anything. Press Disconnect to end a connection. Its next request is refused, and connecting again means signing in again.

​
Audit log

“Changes to members, keys, projects, alerts and reports, newest first. Kept for 24 months.” Owners and admins can read it.

Invite your team

The first invitations, step by step.

Authentication and scopes

How a key is sent and what each scope opens.

Connect Claude

Add the MCP address to Claude and sign in.

White label

The agency-only section of this screen.