Workspaces and team
How a workspace is organized, what each role can do, how invitations and seats work, and how to group and change many sites at once.
Last reviewed
On this page
A workspace is where one company or agency keeps its sites, heartbeats, status pages, notifications and team. This page covers how workspaces are organized, what each role can do, how invitations work, and how to organize and change many sites at once.
One workspace per company
Create one workspace for each company or agency that uses OctoPing, and keep all of its clients inside it. Sites, plan limits and billing belong to the workspace. They are never shared between workspaces and never pooled across the people in one.
- A person can belong to many workspaces, with a different role in each. The workspace switcher in the header changes between them and has a Create Workspace option.
- A person can own 1 workspace that has no paid plan. To create another, subscribe the first one to a plan or delete it. Being invited to other people's workspaces is unlimited at any role.
- The 14-day trial belongs to the person and starts with their first workspace. A workspace created after that starts without a trial, so it needs a plan before it can monitor.
- A workspace name can be up to 50 characters. Admins and Owners rename it under Settings.
Roles
Every member has one role in a workspace. Each role includes everything the roles below it can do. The Owner is the person accountable for the workspace and its billing, and every workspace has exactly one.
| Role | Meant for | Takes a seat |
|---|---|---|
| Owner | The person who holds billing and can hand the workspace over or delete it. | Yes |
| Admin | People who run the workspace day to day, including its team and settings. | Yes |
| Member | People who set up and manage monitoring. | Yes |
| Viewer | People who only need to read. | No |
| What you can do | Viewer | Member | Admin | Owner |
|---|---|---|---|---|
| See every site, heartbeat, status page, notification and log in the workspace | Yes | Yes | Yes | Yes |
| Add, edit, turn on and off, and check now sites and heartbeats | No | Yes | Yes | Yes |
| Create, edit, test and delete notifications | No | Yes | Yes | Yes |
| Create, rename and reorder groups, and move sites between them | No | Yes | Yes | Yes |
| Enable, disable, move or change the interval of many sites at once | No | Yes | Yes | Yes |
| Create and edit status pages, their items and incidents, maintenance windows and contacts | No | Yes | Yes | Yes |
| Delete sites, heartbeats, groups, status pages and incidents, in bulk or one at a time | No | No | Yes | Yes |
| Set or clear a status page's custom domain, and change its subscriber settings | No | No | Yes | Yes |
| Export or remove a status page's subscribers | No | No | Yes | Yes |
| Invite people, resend or revoke invitations, change roles and remove members | No | No | Yes | Yes |
| Change the workspace name and history retention, and connect or disconnect Slack | No | No | Yes | Yes |
| See the plan, the usage and the billing state | No | No | Yes | Yes |
| Choose a plan and open the billing portal | No | No | No | Yes |
| Transfer ownership and delete the workspace | No | No | No | Yes |
When someone without the role tries an action, the request is refused and nothing changes. The app hides most buttons a role can't use. Where it shows one, such as billing, it names the person who can.
Seats
A seat is an Owner, Admin or Member. Viewers are free and unlimited on every plan. The number of seats comes from the plan, and the pricing page lists it for each one.
- A pending invitation for an Admin or Member counts against the seats from the moment it's sent, so a workspace can't send more invitations than it has seats.
- Moving a Viewer up to Member or Admin takes a seat. Moving between seat roles, or down to Viewer, never does.
- A full workspace is refused with a message that says so. Invite as a Viewer, remove a member you no longer need, or choose a larger plan.
Invite a team member
An Admin or Owner opens Settings and chooses Invite Member, then enters an email address and picks Admin, Member or Viewer. An invitation can't grant the Owner role.
- OctoPing emails the person a link. If the address already has an OctoPing account, following the link adds the workspace to it.
- If it doesn't, the link opens a registration form. The email address on that form is fixed to the one that was invited and can't be changed, so only that address can use the invitation.
- A link works once and expires 30 days after it was sent. Resend from the pending invitation's menu issues a new link and starts the 30 days again.
- Pending Invitations lists each invitation with Resend and Revoke. A revoked invitation can no longer be used.
- Each address can have one invitation per workspace. Inviting it again replaces the earlier one.
Change a role, remove someone, transfer ownership
- Admins and Owners change a role from the member's menu with Change Role, and take someone out with Remove. Nobody can change their own role or remove themselves.
- The Owner can't be removed or given another role directly. Transfer ownership first. Choose Transfer Ownership in the Danger Zone and pick the new Owner from the members. The previous Owner becomes an Admin. This is how the workspace always keeps exactly one Owner.
- Only the Owner can delete the workspace, and nobody can delete the last workspace they belong to.
Groups
Groups organize the Websites list, and a group per client is the usual way agencies use them. Groups hold sites only, and every member can still see every group.
- Choose Manage Groups on the Websites page to create, rename or delete groups. Group names are unique within the workspace.
- Move a single site from the Move to group item in its row menu, or select several sites and choose Move to group in the bar that appears. Ungrouped takes them out of a group.
- Deleting a group doesn't delete its sites. They become ungrouped.
- The group filter at the top of the list narrows it to one group or to Ungrouped.
Bulk actions
Select sites with the checkboxes on the Websites page and a bar appears. A single request covers up to 100 sites.
| Action | Role | What it does |
|---|---|---|
| Move to group | Member | Puts the selected sites in one group, or takes them out of any group. |
| Enable | Member | Turns monitoring on for the selected sites. |
| Disable | Member | Turns monitoring off. A disabled site isn't checked and sends no alerts. |
| Check interval | Member | Sets the HTTP check interval for the selected sites. The options your plan doesn't sell are greyed out. |
| Delete | Admin | Removes the sites with their history and notification settings. This can't be undone. |
- A site from another workspace is skipped and never touched. When some of the selection was skipped, the page reports it, for example that 3 of 5 websites were updated, so a partial result doesn't look like a full one.
- Enable and Disable never create a site, so they work on a workspace that's at its site limit. Check interval is checked against the plan first, and the page says so when the plan doesn't sell the interval.
What a bulk delete removes
Deleting a site removes its check history and its notifications. Status pages that showed it lose that item. Deleting is also how a workspace that's over its limit gets back under it.
Related pages
- Plans and billing covers seats, the trial and who can pay.
- Status pages explains how to give a client their own view.
- Alert rules describes who can create notifications and what they send.
- Contacts covers adding clients as alert recipients without a login.
Related
- DocsPlans and billingWhat counts as a site, how the trial and a pause work, how to subscribe, what a failed payment or a cancellation does, and how history retention is handled.
- DocsStatus pagesCreate, brand and publish a status page, choose what it shows and run an incident from first update to resolution.
- DocsContactsAdd your clients to a status page so they get every alert for its sites and a monthly summary: consent, what is sent, when and how a contact leaves.
- ForWebsite monitoring for agencies: all client sitesMonitor client websites with every check on each site, a white-label status page per client, and client contacts who get alerts and a monthly summary without a seat.