Teams.

A team is a smaller named group inside an organization. Use one to share a project or a database with exactly the right people in a single move — no per-person fiddling.

What a team is

Every team belongs to one organization, and every team member is also a member of that org. A team is always a subset of its org. So when you add someone who isn’t in the org yet, Orchid invites them to the org and the team together — more on that below.

Teams exist to slice a big org into the groups that actually work together — say a marketing-analytics team and a finance team inside one company. Share once with the team and everyone in it gets access; nobody outside it does.

Team roles

Each team member holds one of three roles:

• Lead — manages the team: rename it, edit the roster, and manage the team’s connections, env vars, and projects.
• Developer (the default) — creates and runs projects, and uses the team’s shared connections and env vars.
• Viewer — read-only. A viewer can see the team’s work but cannot use a shared connection’s credential.

An org owner or admin can manage any team in the org. A team lead manages only their own team.

Create a team & add members

1. Open your org on the web dashboard at orchidide.com/orgs and go to the Teams tab.
2. Click New team (owner/admin only) and give it a name.
3. Open the new team and go to its Members tab.
4. Click Add member, then pick an org member to add them instantly, or type an email to bring in someone from outside the org.

Adding someone who’s already in the org is instant — no acceptance step. Type the email of someone who isn’t in the org yet and you send one invitation that covers both: when they accept, they join the organization and land on this team in a single step. From the Members tab you can also change a member’s team role or remove them. Anyone can Leave a team — that removes them from the team only, not from the org.

What a team gives you

• Share a project with the whole team at once — see Sharing. Managers can also spin up a blank team project that’s shared with the team the moment it’s created.
• Give the team a shared database connection to query, without anyone handling the password.
• Store shared environment variables — keys and secrets that drop into your project runs automatically. See Secrets & env vars.
• A shared Activity feed and Metrics, so everyone can see what changed and how the team is being used.
• Per-member Notification preferences — choose what you get notified about. In-app and Slack are the working delivery channels.

The team page

Each team page has its own set of tabs:

• Overview — the team at a glance: members, shared projects and connections.
• Metrics — usage and growth insight from activity and membership.
• Members — the roster, where you add, remove, and re-role people (plus pending invitations).
• Projects — every project shared with the team, and New project for managers.
• Connections — the database connections the team can use.
• Env — the team’s shared environment variables (managers only).
• Activity — a running log of what happened in the team.
• Notifications — choose which events you get notified about.
• Settings — rename the team, and leave the team from here.

Where to next

• Connections — give a team a shared database to query.
• Secrets & env vars — shared credentials and keys, protected.
• Sharing — share a published project with a team.
• Organizations — the overview, and how orgs and teams fit together.