Organizations & teams.

Organizations let you share projects and databases with a whole group at once, instead of adding people one email at a time. You manage them on the web dashboard at orchidide.com — not in the desktop app.

What an organization is

An organization is a named group of people you share things with. It’s a sharing target, not an owner — your workspaces and projects still belong to you, and the org doesn’t take them over. The point is reach: grant access once and everyone in the group gets it. When someone joins later, they inherit whatever the group already has — no re-sharing, no chasing down a list of names.

Organizations live under the Organizations section of the web dashboard, at orchidide.com/orgs. Everything on this page happens there.

Organizations vs. teams

An organization is the whole group. A team is a smaller, named subgroup inside it — say Growth or Data Platform — made up of a subset of the org’s members. Share with the org when something is for everyone; share with a team when it’s for a slice. Every team belongs to exactly one org, and every team member must also be an org member. More on building them out in Teams.

Roles

An organization has three roles:

• Owner — full control, including deleting the org and transferring ownership.
• Admin — manage members, teams, connections, invitations, and settings.
• Member — view and use what they’ve been given.

An org always keeps at least one owner — the last owner can’t be removed, demoted, or leave. Teams have their own roles (lead, developer, viewer); see Teams for what each one can do.

Create an organization & invite people

1. Go to orchidide.com/orgs.
2. Click New organization and give it a name.
3. You become the owner and land on its dashboard.
4. On the Members tab, click Invite a member, enter an email, and pick a role.

Inviting sends a pending invitation, not instant access. Your teammate sees it the next time they open their Organizations page and clicks Accept (or Decline). If their email already has an Orchid account the invite reaches them right away; if they haven’t signed up yet, it waits and attaches itself when they create an account with that same email.

The org dashboard

Each organization gets its own dashboard with a strip of tabs across the top. Each one covers a different part of running the group:

• Overview — a snapshot of the org: members, teams, connections at a glance.
• Metrics — usage, growth, and security insight drawn from activity.
• Teams — create and manage the subgroups inside the org.
• Members — the roster, plus any pending invitations waiting to be accepted.
• Connections — shared and template data sources (owner/admin only).
• Activity — a log of what happened and who did it.
• Settings — the org name, ownership, and how you leave.

Where to next

• Teams — subgroups and the roles inside them.
• Shared connections — one database, the whole team.
• Secrets & env vars — how the vault protects passwords and keys.
• Sharing projects — grant a project to a group.