Common Team Workflow Scenarios

This guide covers practical team collaboration scenarios in StatusDrift, showing how to configure permissions and workflows for common organizational structures. Use these examples as templates for your own team setup.

Scenario 1: Multi-Team Organization

Situation: Your company has multiple engineering teams (Backend, Frontend, Infrastructure), each responsible for their own services and status pages.

Recommended Setup

1. Create Groups for each team: “Backend Services”, “Frontend Services”, “Infrastructure”
2. Assign team leads as Members with Editor permission on their respective groups
3. Assign team members as Members with View or Editor permission based on their responsibilities
4. Create one Admin or Global Editor for the DevOps lead who needs cross-team visibility

Example Configuration

Scenario 2: Agency Managing Multiple Clients

Situation: You are an agency managing monitoring for several clients. Each client should only see their own infrastructure.

Recommended Setup

1. Create a Group for each client
2. Agency staff get Global Editor or Global Viewer roles depending on their function
3. Client contacts get Member role with View permission on only their group
4. Client technical leads can get Member role with Communication permission to post updates

Example Configuration

This ensures complete client isolation while giving your team full operational control.

Scenario 3: Follow-the-Sun Support

Situation: Your support team operates across multiple time zones. Each regional team needs to handle incidents during their shift.

Recommended Setup

1. All support staff receive Global Communication role
2. Shift leads can have Global Editor if they need to modify monitors
3. Engineering teams remain as Members with Editor access to their groups

Example Configuration

The Global Communication role allows any support team member to create and update incidents regardless of which team owns the affected services.

Scenario 4: Enterprise with SSO

Situation: Your enterprise uses Okta (or another IdP) and wants to automate team member provisioning and role assignment.

Recommended Setup

1. Configure SAML SSO following our SAML integration guide
2. Enable JIT provisioning to auto-create accounts on first login
3. Set up group mappings to automatically assign roles based on IdP groups
4. Enforce SAML authentication for your email domain

Example Group Mappings

When employees join or leave teams in your IdP, their StatusDrift permissions update automatically on next login.

Scenario 5: External Stakeholder Access

Situation: Executives, investors, or partners need visibility into your uptime metrics without the ability to make changes.

Recommended Setup

1. Assign Global Viewer role to stakeholders who need to see everything
2. Assign Member with View permission to stakeholders who should only see specific services
3. Consider using public status pages for truly external parties who do not need accounts

Example Configuration

Scenario 6: Contractor or Temporary Access

Situation: You need to grant temporary access to contractors or consultants working on specific projects.

Recommended Setup

1. Create a project-specific Group if one does not exist
2. Invite contractors as Members with only the necessary group permissions
3. Document the access grant with start and end dates
4. Set a calendar reminder to revoke access when the contract ends

Tip: Never grant global roles to temporary staff. Always use the Member role with specific group permissions to limit exposure.

Workflow Best Practices

Onboarding New Team Members

1. Determine which groups they need access to
2. Decide on the appropriate permission level (View, Editor, Communication)
3. Send the invitation with the correct role
4. Have them verify they can access the expected resources

Offboarding Team Members

1. Remove the user from StatusDrift collaborators
2. If using SSO, disable their IdP account (access is revoked automatically)
3. Review any active incidents they were handling
4. Transfer ownership of any resources they managed

Periodic Access Reviews

Schedule quarterly reviews to ensure permissions remain appropriate:

• Check that former employees and contractors have been removed
• Verify that role assignments match current responsibilities
• Review group memberships for accuracy
• Update documentation for any changes made

Getting Help

If you need assistance configuring team permissions for your specific use case, contact our support team at [email protected]. We can help you design a permission structure that meets your security and operational requirements.