Invite team members by clicking your avatar in the top right corner of the management interface > Users > Add user.
STATUSFY HIDE ICON UPDATE
Invite your support team, ops team, or others so they can also update the status page when things go wrong. Invite a team member - Recruit others to help. Details on components.īackfill historical incidents - If you're migrating to Statuspage from another tool, you can add your previous incidents as a "Backfilled incident". Click Components from the sidebar to create your components. You can be up and running with a new status page in a matter of minutes.Ĭreate components - Components are the functioning pieces of your website or application such as your API, mobile app, help center, and admin tool. Choose what components and information is visible so that users and groups see only what is of interest to them.
STATUSFY HIDE ICON FULL
Private Page trials are limited to 30 days with full functionality.Īudience-specific page functionality - Audience-specific pages have set permissions for what users and groups can view and what notifications they can receive. We support SAML 2.0 and Google Auth for private pages. Page viewers must log in with credentials in order to view the page.
Private page functionality - Private pages are hidden behind authentication. The only restriction is that you must be a logged-in team member in order to view the page. Public page functionality - Public pages are viewable by anyone with an internet connection. Audience-specific pages are for prespecified users and groups to view. Private status pages are for communicating internally with employees and stakeholders. Public status pages are for communicating with external customers. Anytime an incident is posted, a banner will surface on your site. Read up on the Service Recovery Paradox.Įmbed your system status in-app - Using our Status embed, you can embed your system status directly in your website, app, or help center. Customers expect a certain level of transparency these days. Better to sort this out Day 1, before the first live incident.Īdopt a culture of transparency - Gone are the days when downtime was something you kept hush-hush. This is crucial for initial implementation and longevity.
Rally the troops - Define which team(s) and roles own the Statuspage. Is this for internal or external communication? Should everyone receive the same updates or do certain issues only affect certain end-users. Set expectations with your team, and communicate with your customers so they know what's coming.ĭefine your page type - Make sure you know how you intend to use Statuspage. Keep them in the loop when servers and systems are down. IT teams - Employees and students are becoming more and more dependent on workplace/school technology. Operations teams - Pipe your performance metrics and system status into Statuspage so your team has a dedicated place to reference any time. This leads to angry customers, and a burnt-out support team. Don't leave your customers in the dark and don't bog down your support team with repeat tickets. Support teams - Deflect support tickets by using Statuspage to communicate with your customers when you're down. Bring your team together and focus on the important things using Statuspage. Support teams, ops teams, and IT teams use Statuspage to communicate incidents and outages. Statuspage Basics Teams that use Statuspage You'll find links to more detailed knowledge base articles embedded throughout this guide. We hope this helps new and potential users get familiar with our product, and discover new ways of using Statuspage. This guide is meant to be a one-stop shop for a high-level overview of Statuspage.
0 kommentar(er)
