Team and roles
Your team runs the workspace from the dashboard. Each member is an owner or an admin: admins do the daily work, and owners also decide who's who and what the workspace pays for.
What each role can do#
| Owner | Admin | |
|---|---|---|
| Posts, comments, review, customers, companies, the roadmap, the changelog, boards and tags | Yes | Yes |
| Settings: general and portal, AI, branding, widget, sign-in, traits | Yes | Yes |
| API keys, webhooks, Slack and Discord | Yes | Yes |
| Invite admins, and remove admins | Yes | Yes |
| Invite owners, remove owners, change roles, transfer ownership | Yes | No |
| Change the workspace's slug | Yes | No |
| Add or remove a custom domain | Yes | No |
| Subscribe, and manage billing | Yes | No |
Admins still see the Billing page and the custom domain's status. Each member chooses their own email notifications.
An API key acts with the access it was given, read or write, and never more than its creator's role allows today. When its creator leaves the team, it stops working.
Invite someone#
Under Settings → Team, Invite someone takes an email address and a role. Admins invite admins; owners invite admins or owners.
- The invitee gets an email, signs in to Swingback with that address, and accepts the invitation on their home page, or declines it.
- An invitation is valid for 7 days. Resend sends it again and renews it for 7 days, up to 3 times an hour. Withdraw cancels it. Only owners resend or withdraw an invitation to become an owner.
- An address can have one pending invitation, and someone already on the team can't be invited.
- Pending invitations count toward your plan's members, like members do: up to 3 on Free, 20 on Pro. See Plans and billing.
Change roles and ownership#
Under Settings → Team, the menu on a member's row has what your role allows:
- Make owner or Make admin: owners.
- Transfer ownership: owners. They become an owner and you become an admin.
- Step down to admin, on your own row: owners.
- Remove from workspace: owners remove anyone, and admins remove admins. They lose access at once, and the API keys they created stop working.
Leave a workspace#
Leave workspace is under Settings → General, and in the menu on your own row under Settings → Team. You lose access, the API keys you created in the workspace stop working, and coming back takes a new invitation.
The last owner#
A workspace always has an owner. The last one can't leave, be removed or step down to admin: make another member an owner first.
Sign in#
Your team signs in with their email address: a 6-digit code arrives by email, valid for 10 minutes, with a link that signs in too. Signing in with a new address creates the account.
When offered, Continue with Google and Continue with GitHub work too. They take an email address the provider has verified, and sign in to the account with that address, or create it.
One account works in every workspace you belong to.
Sessions#
Your Account page, from the account menu at the top right, lists where you're signed in: each browser, when it signed in and when it was last active. Sign out ends any of them, the current one included. A session ends after 30 days without use, and 90 days after signing in at most.
The Account page also sets the name your teammates see. It shows the email address you sign in with, which it doesn't change.