Your agent (MCP)
Team access
Who on your team can connect an agent to nextanalytica, what the owner, admin and member roles allow, and how a person's or a key's access ends.
Updated
Every person connects their own agent, as themselves. There are no shared keys to pass around: an agent sees what its person can see, and nothing more.
What can each role do?
| Role | Their agent can |
|---|---|
| Owner | Everything, including deleting the project. |
| Admin | Read, and change tracking, sources, conversions, connectors, team instructions and who has access. |
| Member | Read, use skills, and add notes and memories. |
Invite people in Access. They sign in with their own Google, GitHub or email account.
How does access end?
| What you do | What happens |
|---|---|
| Remove someone in Access | Their agent loses access to the project and its connectors at once. |
| Revoke an agent key in Access | That key stops working at once. |
| A key reaches 90 days | It stops working; make a new one. |
| Remove the server in the client | That client stops calling us; the sign-in stays valid elsewhere. |
Do you support single sign-on or managed authorization?
Not today. Each person signs in with their own account. If your company needs SSO or centrally managed access for agents, tell us at hello@nextanalytica.app.