Skip to main content
A team is the container for everything in Nuphos — connected runtimes, infrastructure accounts, agents, plans, and memory all belong to it. You get a team automatically the first time you sign in, and you grow it by inviting colleagues.

​
Inviting members

In the team’s Settings → Members, invite people by email and assign a role. Pending invitations show until they’re accepted. Administrators can change a member’s role or remove them at any time.

​
Roles

Every member has one of three roles:
Connecting a connector requires the Administrator role. Pair roles with per-account member allow-lists to control who can use which account.

​
Your team ID

Each team has an ID, shown in the team’s Settings → General. You’ll need it when you set up cloud trust policies — for example, the AWS OIDC trust condition pins your role to nuphos:team:<your-team-id>. See Connect AWS.

​
Team settings

Administrators manage team cloud/tool connections under Connectors and team name, members, billing and shared guidance in team Settings. Messaging setup starts from the relevant connector; it is not an iMessage settings flow.

​
Membership, conversation access and computer access

Team membership is not automatic access to every private session. A conversation has its own sharing controls and invited participants. The computer also has an access policy; someone invited into a conversation may still need permission to use its runtime’s machine before contributing. See Agents. Team skills, instructions and memory are shared knowledge. Personal credentials and personal settings are separate. Review the scope before saving information or sharing a machine with its existing CLI sign-ins.

​
Settings you share

Team Settings groups General, Members, Billing, Instructions, Skills, Memories, Triggers, Archived agents and Audit log. My preferences contains personal instructions, setup synchronization and runtime fallback. Account settings hold Personal Credentials; This computer holds Local exec and Local runtime.