> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Who on our team can create, manage or post to status pages?

By default, creating or configuring status pages is an administrative function in [incident.io](http://incident.io/). Typically, **workspace admins or owners** have the permissions to create new status pages, adjust settings (like components, domains, etc.), and delete or archive pages. Regular team members (responders) usually cannot create a new status page without the appropriate role permission.

However, once a page is set up, incident updates to that page can be made by incident responders (for example, an incident commander can publish updates to a public status page during an incident) – you wouldn’t want only admins to be able to post updates, since that would bottleneck communications.

So the model is generally: admins set up and maintain the page configuration, whereas **incident leads or communication leads can publish updates** to the page during an incident.

<img src="https://mintcdn.com/incidentio-18bb4170/YyaXj7lNF5_8OSsE/images/help-centre/who-on-our-team-can-create-manage-or-post-to-status-pages/screenshot-1.png?fit=max&auto=format&n=YyaXj7lNF5_8OSsE&q=85&s=03367b6606763e31176a41455e2f109f" alt="Screenshot 2025-05-13 at 12.45.50.png" width="576" height="654" data-path="images/help-centre/who-on-our-team-can-create-manage-or-post-to-status-pages/screenshot-1.png" />

The specific roles and permissions can be fine-tuned in [incident.io](http://incident.io/) ’s settings (for instance, you may define which user roles are allowed to publish to a status page).
