Set up the workspace

You created the workspace, so you are its owner and a kcap admin. Administration is in your avatar menu; it opens on People → Members. Nothing here needs to be done before people start storing sessions, but three things are worth doing on day one

1. Invite the first people

People → Invitations: an email address and a role, Member or, for owners, Admin. Kurrent emails a link valid for seven days; the person signs in through single sign-on and joins with that role. Invitations and active members both count against the plan’s seats. People, roles and teams

Point them at Join a kcap workspace; they do not need the URL

2. Decide the organisation’s default visibility

Members’ sessions default to org_public, which means readable by the organisation for the organisation’s own repositories. Which repositories count is yours to set: General → Sessions → Org-visible sessions, a comma-separated list of GitHub organisation or user names. Blank uses the connected GitHub account. Without it, org_public sessions stay private. Sessions and repositories

3. Check what AI is doing the work

Titles, outcome summaries, embeddings and evaluations run on Kurrent-managed AI on every plan, with nothing to configure. Add your own provider keys under AI & models → AI Providers when you want a particular vendor or model, and decide whether sessions are evaluated automatically under Evals. AI providers and models

Optional, any time

• Teams, for sharing sessions with a named group. People, roles and teams
• Slack, for link previews and direct-message notifications; a wizard that takes about two minutes. GitHub and Linear credentials, for work-item enrichment. Integrations
• Machine credentials, for CI runners. Store sessions where nobody can sign in
• Projects, which members create themselves from the scope selector on Team and Enterprise plans

The getting-started checklist

Administration → Getting started (/admin/getting-started) lists the setup items for the workspace with a badge of how many required ones are done. Members have their own checklist under Get set up in the avatar menu

Who can do what

Owners and organisation admins manage members, invitations and the plan. The other console pages need kcap administrator access; on a shared deployment an organisation admin does not automatically have it. An owner can promote, demote and transfer ownership from Members. A locked-out workspace can be recovered by the operator with the deployment’s Auth:Admin:UserIds setting

Settings saved in the console are stored encrypted and take effect without a restart; a field supplied by the deployment’s environment is shown locked