Skip to main content

​
Team Structure

Unlimited Team Members

Invite as many teammates as you need on paid plans.

Role-Based Access

Assign roles to control what each member can do.

​
Inviting Team Members

1

Open team settings

Go to Settings → Team in your dashboard.
2

Send invitation

Enter the email address and select a role. An invitation email will be sent.
3

Member accepts

The invitee clicks the link in the email to join your team.
Invitations expire after 7 days. If an invitation expires, you can resend it from the team settings.

​
Team Roles

​
Owner

  • Full access to all team features
  • Manage billing and subscription
  • Can delete the team

​
Admin

  • Manage forms and workflows
  • Invite and remove members
  • Change member roles
  • Manage billing and subscription
  • Cannot delete the team

​
Editor

  • Create and edit forms
  • View submissions
  • Cannot manage team members or settings

​
Viewer

  • View forms and submissions only
  • Cannot create, edit, or delete anything

​
Managing Members

  • Change Role — Click the member’s role dropdown and select a new role.
  • Remove Member — Click remove and confirm. The member loses access immediately.

​
Team Profile

  • Team Name — Display name for your team (visible to members).
  • Team Icon — Optional avatar or logo for your team.
  • Team ID — Unique identifier used for the API and integrations. The first 8 characters appear in your form URLs (/r/{team-id}/{slug}).

​
Audit Log

Owners and admins can see who did what in the workspace under Settings → Audit log: sign-ins and failed sign-ins, invitations, role changes and removals, exports, bulk and permanent deletes, settings changes, API keys, webhooks and connected apps. Filter by category, person, who did it (a person, an API key, an app or Orbit itself), date range or free text, open an event for its details (IP address, device and what changed), and export what the filters match as CSV. Events are kept indefinitely. What the log can and can’t see:
  • Sign-ins are recorded whenever a session starts, however the person signed in (password, Google or a magic link), with the IP address and device. Each sign-in shows up in every workspace the person belongs to.
  • Failed sign-ins are recorded when Orbit’s sign-in page or two-factor step reports them, because the password and code are checked by the sign-in service rather than by Orbit. Attempts made against the sign-in service directly, and Google sign-ins that Google refuses, aren’t visible to Orbit.
  • Changes are recorded once they succeed. A refused change, such as a delete a member wasn’t allowed to make, isn’t logged.
  • Privacy: when someone deletes their Orbit account, their events stay (with their name) but their IP addresses and devices are removed. When a contact’s data is erased on request, the events about that contact keep only a masked identifier.
  • Failed sign-ins are capped at a few per account every 15 minutes, so repeated attempts can’t flood the log.
  • Secrets never appear in the log: API keys, webhook secrets and tokens are left out, and webhooks show only their host.

​
Next Steps

Account Settings

Manage your personal account

Creating Forms

Build your first form