Everyone8 min read

Sign up your team for Cognition enterprise cloud

Request managed enterprise onboarding, connect an existing workspace, and invite every teammate with their own key. Includes copyable prompts for the workspace owner and each teammate.

Set up one shared workspace for your organization, then invite people into it using their own identities. This guide is for the person arranging an enterprise cloud plan and for teammates joining an enterprise workspace that is already active.

Note

Enterprise onboarding is managed. The public pricing page currently routes organizations to Cognition Teams and “Book a managed pilot”; it does not offer a self-serve Enterprise Cloud checkout. Confirm your enterprise plan, workspace, and commercial terms with Cognition. Creating an account, minting a key, or accepting an invite does not purchase or activate an enterprise plan.

Choose your starting point

Need a plan for the whole organization? Start with managed onboarding below.
Already have an enterprise plan? Ask your Cognition contact or workspace owner to confirm the active workspace, then follow the invitation steps.
Received an invite? Go straight to “Join as a teammate.” You do not need to purchase a separate individual plan to follow the invitation flow.

1. Arrange your enterprise cloud plan

1Choose a workspace owner who will coordinate onboarding and a billing contact who can confirm your organization's purchasing requirements.
2Open Pricing, find Cognition Teams, and choose “Book a managed pilot.” The booking page lets you arrange a conversation with Cognition.
3Bring your organization name, expected team size, coding agents, desired rollout date, and any security or deployment requirements. If you already use Cognition, bring the workspace name so onboarding can build on the correct brain.
4Confirm the plan, price and billing schedule, included access, and any agreed security or support requirements with Cognition before purchase. Do not assume that SSO, automatic user provisioning, dedicated hosting, or a specific service level is included.
5Before a company-wide rollout, confirm which workspace has the agreed enterprise access. Keep that workspace name in the invitation checklist so teammates do not create separate brains.

Copy this planning prompt

Help me prepare a Cognition enterprise cloud rollout for my team.

Organization: [company name]
Team size: [number of people]
Workspace owner: [name]
Coding agents: [Claude Code, Codex, Cursor, Gemini, or other]
Existing Cognition workspace: [workspace name, or not yet created]
Requirements to discuss: [security review, access controls, billing, or support]

Review https://www.lamlab.ai/pricing and help me prepare for managed onboarding at https://www.lamlab.ai/builders.
If we already have an enterprise agreement, help me confirm the intended workspace with our Cognition contact before inviting anyone.
Do not buy individual Pro plans for teammates, create duplicate workspaces, or claim enterprise activation is complete without confirmation.
Prepare a rollout checklist. Ask me before sending invitations, accepting terms, making a payment, or changing access.
Never request or include API keys, passwords, or confidential company data in the checklist.

Replace the bracketed details. This prepares the rollout; it does not sign a contract, make a payment, or activate a plan.

2. Invite people into the same workspace

Once the intended workspace is ready, the owner can create a join link and a ready-to-share prompt in the org workspace. Use an authorized key for that workspace, and keep it private.

1Open the org workspace. If prompted, enter your own authorized Cognition key privately and select “Open.” Confirm the workspace name before proceeding.
2Choose “Create invite” in the teammate invite area, then “Copy prompt.” The generated prompt includes the real join link and setup steps.
3Share the invite privately with the intended teammates through your approved company channel. Do not send your API key or owner recovery key.
4Check the invite page for its role, expiry date, and remaining uses. Create additional invite links as needed for the rest of the team.

Open the org workspace

Note

Standard invites currently expire after 30 days and allow up to 25 redemptions; scoped invite packets can have a smaller limit. The invitation's use limit is not your purchased seat allowance. Check your agreement with Cognition for the scope of your plan.

Heads up

Treat a working invite link as access to your workspace. Do not publish it in public docs, a public repository, or an open community channel. Review who should join before sharing it.

3. Join as a teammate

1Open the invite supplied by your workspace owner. Confirm that the page names the team you intended to join.
2Continue through the invite setup and sign in using your own identity. If you already use Cognition, use the same identity rather than creating a duplicate account.
3Follow the setup flow to mint your own personal cog_me_* key for this team brain. If the flow reports an existing key, follow its recovery or reuse instructions instead of creating a second workspace.
4Choose your coding agent and follow the setup instructions generated for it. Keep the full key private and store it only in the intended local credential configuration.
5Restart the agent if needed so it loads the Cognition tools. Keep the invite link until setup is complete; if sign-in is interrupted, reopen that same link to resume.

Tip

A personal key can belong to the shared team workspace. The cog_me_* prefix identifies an individual's key; it does not by itself mean a separate solo brain. Each teammate should use their own key so authorship and activity stay attributable. Do not distribute one cog_live_* owner key to the whole team.

Copy this teammate setup prompt

Help me join my team's existing Cognition cloud workspace.

Team: [team name]
Invite page: [paste the private invite URL provided by your workspace owner]
My coding agent: [Claude Code, Codex, Cursor, or Gemini]

1. Help me open the invite and confirm that the workspace name matches my team. If the invite is invalid, expired, revoked, or used up, stop and ask me to get a fresh invite.
2. Guide me through signing in with my own identity and finishing the invite setup. Keep the invite context. Do not create a separate workspace or subscribe me to an individual plan.
3. I will handle my personal Cognition key privately. Do not ask me to paste it into chat, display it, or save it in a shared file. Do not use another teammate's key or the owner's recovery key.
4. Help me follow the setup instructions generated for my selected agent, then restart it if needed. Preserve unrelated agent configuration.
5. Verify that get_pedagogy_instructions, cognition_assist, and cognition_save_skill are available. Use the read-only connection checks to confirm my workspace without exposing credentials.
6. Ask me for one approved team skill to test. Confirm whether it can be retrieved in this workspace. Do not save a test skill or upload files automatically.
7. Report what passed and any remaining blocker. Do not claim that signing in or installing Cognition activated an enterprise plan.

Use this with an agent you trust with the private invite link. The org workspace's generated “Copy prompt” is another option and already includes the correct invite URL. Never put a real API key in either prompt.

4. Verify the rollout

Each teammate can see the Cognition tools: get_pedagogy_instructions, cognition_assist, and cognition_save_skill. A fresh chat alone may not refresh a cached tool list; restart the agent when needed.
Ask the agent to check its connection and current workspace without displaying the key. Match the workspace to the one your owner confirmed.
The owner can review the People list in the org workspace and check that teammates have appeared. Membership, installs, and key activity are different checks; an invite redemption alone does not prove an agent is connected.
Test retrieval of one known, approved team skill in a second teammate's agent. If it is missing, check workspace membership and skill visibility before changing credentials.
Before the first new skill is saved, review the full draft and its sharing scope. Do not upload secrets, raw emails, private transcripts, or unrelated personal data during onboarding.

What you see	What to do
Invalid, expired, revoked, or exhausted invite	Ask the workspace owner for a fresh link. Do not choose “Start without this invite” when your goal is to join the existing team.
The wrong workspace, or a warning that a new brain will be empty	Stop and check with the owner. Reopen the correct invite instead of creating another workspace.
An existing key or identity conflict	Reuse or recover the existing setup through the options shown. Ask Cognition for help if the correct identity or workspace is unclear.
A plan limit after enterprise onboarding	Ask your Cognition contact to verify the plan on the intended workspace. Do not buy separate Pro subscriptions as a workaround.
Invite creation or portal access fails	Confirm that your key belongs to the intended workspace and that you have the required authority. Do not use another person's key to bypass an access error.
Tools are absent after installation	Restart your coding agent, then check the setup instructions for that host. Share a redacted error with your owner or Cognition contact if the issue persists.

Ready for the whole team

The rollout is ready when the enterprise plan and workspace are confirmed, intended teammates have joined that workspace with individual keys, each agent connects successfully, and a known team skill can be retrieved. Keep billing and access questions with your workspace owner or Cognition contact as the team grows.

Next steps

For teamsRoll Cognition out to your team without the mess Operate & trustTrust but verify: the ledger, stats, health, and privacy

Plan your rollout