Teams & projects

Your team

A team shares one plan, one balance and one member list. Switch teams with the team name at the top of the sidebar. Settings has a project group and a team group: Project details and Members & permissions for the selected project, then Team details, Members and Billing for the team. Members ↗ under Team settings manages who belongs to the team; Members & permissions ↗ manages who belongs to the selected project.

Team roles are Administrator, Editor and Viewer; the owner is listed as Owner and has every administrator right. Administrators manage billing and spending limits and automatically administer every project. Editors manage team settings and members, but cannot change billing or grant or change the Administrator role. Viewers use only the projects they are assigned to. Administering a project does not give access to billing.

Choose the project first

When you name your team during onboarding, Relvo creates its first project, shown as Default. Open the project picker below the team name to search, select or create a project. One project you can access is always selected, and Relvo remembers your last choice in each team.

Custom tools, skills, agents, rules, hooks, folders, secrets, connections and API keys belong to that project. Use separate projects for engineering and marketing, or for applications with different access needs. Getting started also runs inside the selected project.

Project members and administrators

Your team role and your project roles are separate. Everyone in a project uses the same tools, skills, rules and connections. Each project member is an Administrator or a User. Users run what is already configured and can create their own API keys; only project administrators edit resources, including ones a user created earlier. Project administrators manage members in Members & permissions ↗ and settings in Project details ↗.

Tool execution in Project details sets the tools anyone in the project may run, administrators and existing keys included. Connections added in the project, and the operations turned off on them, apply to everyone. The last active project administrator cannot be removed or demoted. Use separate projects when people need different resources.

API-key scopes and additional credential limits still apply in CLI, MCP and API requests. Executable hooks, MCP configurations and permission files are changed by project administrators in the app, never through an API key.

Invite people

In Members ↗ under Team settings, choose a team role for the person you invite. For an Editor or Viewer, tick the projects they will join and choose Administrator or User for each, so one person can administer engineering and use marketing. They are not added to projects you leave unticked or to projects created later. Team administrators automatically administer every existing and new project. A project administrator can also invite someone into the current project from Members & permissions ↗; they join the team as a Viewer.

Each integration uses its own project credential. Switching projects in the app does not move an existing API key or connection to another project.

Switch projects in CLI and MCP

With a saved CLI login, approve each project once in your browser, then switch between the approved projects:

npx --yes @relvo/cli project list
npx --yes @relvo/cli project add
npx --yes @relvo/cli project use PROJECT_ID
npx --yes @relvo/cli tools --query search --project PROJECT_ID
npx --yes @relvo/cli team-skills sync --project PROJECT_ID

project add opens a new approval where you choose the project. project use checks your current access and changes the default; --project on a tool command uses an approved project for that command only. team-skills sync installs that project’s managed files. When you switch, edited files from the previous project are moved to ~/.config/relvo/project-archives/ and the output names each backup. Executable files still require --allow-scripts. Run npx --yes @relvo/cli help project for every flag.

The local MCP that setup registers offers platform_projects and platform_project_select. After selecting a project, reconnect Relvo MCP to load its tools and permissions; until then the old connection pauses API requests. Work already accepted stays in its original project. For ChatGPT or Claude connected by URL, reconnect in the host and choose the project on the approval page. Existing keys and approvals keep their project.

Project limits and existing teams

A team can have 3 projects on Free, 5 on Hobby and 30 on Pro. The plan and balance are shared by the whole team. A team already above its limit keeps its projects; only creating another is blocked. Each project holds up to 10 skills, rules and other items on Free, 50 on Hobby and 100 on Pro; a project above its limit can still edit and delete them, only adding another is blocked.

Teams created before projects existed keep their original project, with its settings, members, keys and connections, and teams with the same owner are not merged. Existing MCP connections, saved OAuth approvals and older CLI logins keep that project without reconnecting.

Delete a project

A project administrator deletes a project at the end of Project details ↗ by typing its name. A team keeps at least one project. Delete triggers registered with an outside app first; a project that still has them cannot be deleted. Deleting stops the project’s members, API keys, MCP approvals, connections and scheduled work; usage and billing records are kept.

If a project has no active administrator, the team owner can make themselves its administrator from Projects without an administrator in Team details ↗. Revoked keys are not restored; create new ones.