Your profile (the account menu › Profile, or Profile inside a project) holds your display name and avatar, the theme (light, dark, system) and the language of CRM & Studio — synced across your devices, as is the document editor's Save / Save and close choice — and the Sign out action.
Theme and language also apply to this documentation site: it shares CRM & Studio's session and preferences.
Personal access tokens#
The Personal access tokens card lets you connect tools that work as you — an MCP client such as Claude Code, a script, curl — without sharing a project token. New token asks for a label, the projects the token may act on (or All my projects, including ones you join later), whether it may use Demo, and an expiry (30, 90 or 365 days, or never). The token (in_…) is shown once, with ready-to-paste snippets for Claude Code, a .mcp.json and curl; afterwards only its first characters are listed.
A token acts with your member rights only, on the projects it names: your role and capabilities in each project are the ceiling, and a platform role is never carried by a token. Connect it to the console's MCP server at https://inmake.dev/mcp (send it as Authorization: Bearer in_…), or exchange it for a project token with POST https://inmake.dev/me/stores/{project}/token {"env": "prod"} — see Personal access tokens.
Each token shows Prod — every token reaches Production — and Demo when it may use Demo too, when and from where it was last used, and the project tokens it currently holds. Revoke ends it at once, together with the project tokens it holds, and deletes it — no history is kept; Revoke all tokens does it for every token. Signing out everywhere does not revoke them — revoke them here. Leaving a project ends the token's access to it, and a disabled account ends every token. An expired token stops working and gives up the project tokens it held (within a day), but stays listed until you Remove it, so you can see why a client stopped working — nothing is deleted without you.