Team members, roles and teams
Workspace access is managed under Settings → Team: who is in, what they can do and which team they belong to.
settings team
Inviting people
Enter an email address, choose a role and press Send invites. Add another invites several at once. Invitees get an email with a link; until they accept they appear under Pending, where you can resend or revoke the invite.
Roles
Role Can
Owner Everything, including billing, deleting the workspace and switching MCP access on or off
Admin Change settings, manage integrations and team, publish knowledge, start Starko AI runs and merge pull requests, save team rules
Member Work on tickets, conversations and CRM records; use Ask Starko with the tools their role allows
Change a role from the menu at the end of a member's row. Removing a member ends their sessions and every MCP connection they made to the workspace.
Teams
Teams group members for routing and reporting: Support, Sales, Engineering. Create teams on the same page and add members. A ticket can be assigned to a team; assignment rules distribute team tickets across members, and tickets nobody can take wait on the team's queue.
Profile and preferences
Each person manages their own name, avatar and password under Settings → Profile, and their notification channels and Starko memories under Settings → Notifications and Settings → Preferences.
Access from other tools
Connecting Claude, Cursor, VS Code or Slack to Starko always happens as a specific person with their role. An owner switches workspace-wide MCP access on under Settings → Integrations → Starko MCP server. See Use Starko from Claude, Cursor and VS Code.
Tips
Keep at least two owners.
Give admins, not members, to people who publish knowledge or run Starko AI.
Create teams before assignment rules; rules route to teams.
Did this answer your question?