Skip to main content
Runa’s team features live inside an organization. Everyone you want to collaborate with — sharing org-wide folders, publishing voice signatures, running workflows together — needs to be a member of the same org. This page covers the invite flow, member roster, and how members leave. For the actual permission matrix, see Roles & permissions.

​
Open the organization panel

  1. In the sidebar, click your avatar at the bottom.
  2. Select View profile.
  3. Scroll to the Your organizations section.
Click an org name to open its inspector. The inspector shows the org name, logo, member count, and (if you’re an Owner or Admin) controls for renaming the org and inviting members.

​
Invite a teammate

From the org inspector, click Invite. The Invite to [Org Name] modal opens with two fields:
  • Email — the address of the person you want to invite (e.g. name@company.com).
  • Role — choose Member or Admin. There’s no Owner option for invites; ownership is transferred separately.
Submit and you’ll see an Invitation sent confirmation showing the email, the role you assigned, and a hint that the invitee will join your org the next time they sign in. A few things to know:
  • Invitations expire in 7 days. If the invitee hasn’t accepted by then, send a new one.
  • You can revoke a pending invitation from the org page at any time.
  • Already-invited errors (HTTP 409) surface as a toast — you’ll see “already invited” rather than a duplicate.
  • Only Owners and Admins can invite. Members don’t see the invite button.

​
Accepting an invitation

For the invitee, accepting is automatic:
  1. They sign in to Runa (or restart the app if already signed in).
  2. They see an incoming invitations modal listing each org they’ve been invited to.
  3. They choose Accept or Decline per invitation.
Accepted invitations attach the user to the org immediately; they’ll see the org in their Your organizations list and in the org switcher.

​
Domain auto-join

If your team’s email domain is verified on your org (via a DNS TXT record), anyone who signs up with a matching email can be auto-joined without a per-person invite. Domain verification is set up by Owners/Admins and uses the standard DNS TXT-record flow. Once verified, new sign-ups whose email matches the domain land directly in the org with the default role.

​
Manage existing members

The Members roster on the org page lists every current member with their avatar, name, email, and role. Owners and Admins can:
  • Change a member’s role — use the role dropdown next to their name. Promotions or demotions involving Owner require an existing Owner.
  • Remove a member — click the trash icon next to their row. Removed members lose access to org meetings and folders immediately.
Two server-side guardrails always apply:
  • You cannot remove the last remaining Owner — the system blocks it.
  • You cannot remove yourself from a roster. Use Leave organization below instead.

​
Leaving an organization

Any member can leave their own org. In the org inspector, click Leave and confirm:
Leave [Org Name]? You’ll lose access to org meetings, folders, and shared voice signatures. You can be invited back later.
After confirming:
  • Your access to org-visibility folders and meetings is revoked.
  • Your private (Personal) meetings are untouched.
  • Any org-wide speaker profiles you contributed remain in the org.
  • An Owner or Admin can re-invite you later.
If you’re the sole Owner, you’ll need to promote another member to Owner first; the system won’t let you leave the org without one.

​
Sign-in providers

Runa authenticates via WorkOS with three options:
  • Google (OAuth)
  • Microsoft (OAuth, with email verification on first sign-in)
  • Magic link (one-time email)
There is no SAML / enterprise-SSO connector exposed at this time. If your organization requires that, contact us at admin@joinruna.com.