Component Group Permissions

By default, every team Editor on a linked status page can work across the whole page. Component group permissions let you narrow that down so a member only sees and manages the groups they are responsible for inside team-facing workflows.

This is useful when different parts of your organization own different parts of your status page — for example, the infrastructure team should only update the “Infrastructure” group, and the payments team should only update the “Payments” group.

How It Works

Permissions are evaluated in this order for component-group-scoped dashboard and incident actions:

1. Status page owner — always has full access. No restrictions ever apply to the account that owns the page.
2. Team Owner or Admin — always has full access, regardless of group restrictions.
3. Group has explicit assignments — if at least one member is explicitly assigned to the group, only those assigned members can access that group inside the team dashboard and incident workflows. Editors assigned as Editor can manage it. Members not assigned to that group do not see it there, even if they are a page-level Editor.
4. Group has no assignments — falls back to the page-level team role. Any page-level Editor can access and manage the group.

Ungrouped components follow a stricter rule: if a member has any explicit group assignments on that status page, ungrouped components are hidden from that member in scoped workflows and cannot be managed by them. Only owners, admins, or editors with no explicit group scope fall back to normal page-level access for ungrouped components.

Setting Up Group Permissions

You must be the status page owner or a team Owner/Admin to manage group permissions.

1. Go to Status Pages → Components in the dashboard
2. Select the status page from the dropdown
3. Find the component group you want to restrict
4. Click the shield icon (🛡) next to the group name
5. The Manage Access modal opens

Adding a member

1. In the modal, select a team member from the Add member dropdown
   • Only Editors and Viewers linked to this status page appear here; Owners and Admins are omitted (they always have access)
2. Choose a Role:
   • Editor — can set component status, add/rename/delete components, and reorder within the group
   • Viewer — read-only; cannot make changes (same as page-level Viewer)
3. Click Add

Removing a member

Click the × button next to any assigned member to remove their explicit assignment.

Removing the last assignment from a group removes all restrictions — the group falls back to page-level role and any page-level Editor can modify it again.

The “Restricted” Badge

When a group has at least one explicit assignment, it shows an orange Restricted badge in the groups list. This is a quick visual indicator that access to this group has been narrowed.

Permission Reference

What Operations Are Covered?

Group permissions affect both visibility and write access inside shared team workflows:

• Viewing components and active incidents in the Simple Dashboard
• Viewing component-linked incidents in incident lists and incident details
• Loading component choices in incident forms and other authenticated component pickers
• Setting or clearing a component’s manual status override
• Creating a new component inside the group
• Renaming a component
• Deleting a component
• Moving a component into or out of the group
• Renaming, reordering, or deleting the group itself

The public status page is not filtered by team assignments. These rules only affect authenticated team-facing tools.

Multi-Group Assignment

A team member can be assigned to more than one group. Each assignment is independent — a member could be an Editor on the “Backend” group and a Viewer on the “Infrastructure” group at the same time.

Plan Limits

Component group permissions are part of the Teams feature. The Teams feature must be enabled on your plan. There is no separate limit on the number of group permission assignments.

See Plans and Billing for details on which plans include Teams.

Troubleshooting

“You do not have permission to modify this component”

You’re a team Editor but the group has explicit assignments and you’re not one of them. Ask the status page owner or a team Admin to add you to the group in the Manage Access panel.

“I can’t see a component or incident I used to see”

That usually means explicit group assignments were added to the status page. Once those assignments exist, scoped members only see their own groups inside the Simple Dashboard, incident lists, incident details, and component dropdowns.

If the missing item is ungrouped, ask the owner or an admin to move it into a group you can access, or remove the explicit scope restriction from your account.

The shield button doesn’t appear

You don’t have management rights for this group. Only the status page owner, team Owners, and team Admins see the button.

I removed the last member but editors still can’t modify the group

After removing the last assignment, the group returns to page-level fallback. Make sure the team member has the Editor role at the page level, then refresh the dashboard or incident form so the new access scope is reloaded.

A member is missing from the Add member dropdown

• Owners and Admins are not shown — they always have access and don’t need an explicit assignment.
• The member may already be assigned (they appear in the current assignments table instead).
• The member’s team may not be linked to this status page.

What’s Next?

• Teams overview
• Managing components and groups
• Status page settings
• Plans and Billing