Getting started
Your personal space and organization workspaces are separate. Personal navigation contains your Home, Referrals, Wallet, $CLAIRE and account settings. An organization's sidebar starts with Home, Token, Community (Telegram), Social (X) and People; then Knowledge, Automations and Developers; then Site, Docs and Assets; and Settings last. Create or choose a workspace for your project. You do not need to link a token to use Telegram, X, Knowledge, or the site.
Create a workspace
- Sign in and create a workspace with a name and unique slug.
- Choose it from your workspace list. The creator becomes its owner.
Owners and admins can use the optional Getting started sidebar checklist. Hide or restore it for the selected organization in Personal settings → Appearance; the preference applies to your account in this browser.
Claire uses a dark interface. Appearance offers preset or custom accent colours for this browser, not an account-wide theme or a change to your public site's appearance.
Invite teammates
- In Settings → Members, invite teammates by email. Owners and admins can send invitations.
- Share the invitation link if email delivery is not configured or the email was not sent. Claire creates the link and attempts to email it when delivery is configured.
Invitation links expire after 7 days. Access to workspace data depends on current membership, not simply having a link.
Understand roles
| Role | What it can do |
|---|---|
| Owner | Manage the workspace, change other members' roles, and transfer ownership. |
| Admin | Manage integrations and content, invite people, and create developer keys. |
| Member | View the workspace and its connected activity; management actions are restricted. |
Only the owner changes another member's role.
Choose your next step
Link a Telegram chat, connect X, or set up your site. You can do these in any order. For optional token tools, verify a wallet and launch or vest a supported token when your chosen network is available.
Building a server or agent integration? An owner or admin can create a developer credential for REST, MCP, or both, then approve the sources it may read.