Teams & Organizations - StatusStack Documentation

Overview

StatusStack uses a hierarchical multi-tenant architecture to support teams of all sizes, from small startups to large MSPs managing hundreds of clients.

Organization (Your Company)
  ├── Team 1 (Engineering)
  │     ├── Stacks
  │     ├── Monitors
  │     ├── Notification Rules
  │     └── Users (Members, Admins)
  ├── Team 2 (Operations)
  └── Team 3 (Client: Acme Corp) → MSP Use Case

Organizations

What is an Organization?

An Organization is the top-level entity in StatusStack that represents your company or business. Everything in StatusStack belongs to an Organization.

Single Tenant

All your data is isolated from other Organizations

Subscription Billing

Subscription and billing are managed at the Organization level

Teams Management

Create multiple Teams within your Organization

Shared Resources

Share Sources and templates across Teams

Organization Settings

Manage your Organization from the dashboard:

Navigate to Settings

Click Settings → Organization in the sidebar

Update Details

Configure Organization information:

Organization Name
Company Website
Contact Email
Time Zone
Logo (for branding)

Manage Subscription

View and manage your subscription:

Current plan (Free, Pro, Enterprise)
Usage statistics
Billing history
Payment methods

Teams

What are Teams?

Teams provide logical separation within your Organization. Teams are perfect for:

Departments - Engineering, Operations, Support
Environments - Production, Staging, Development
Clients - MSP client management (Acme Corp, XYZ Inc.)
Projects - Product A, Product B

Team Hierarchy

Your Organization
  ├── Engineering Team
  │     ├── Production Stack
  │     ├── Staging Stack
  │     ├── 15 Website Monitors
  │     └── Users: Alice (Admin), Bob (Member)
  │
  ├── Operations Team
  │     ├── Infrastructure Stack
  │     ├── 5 Website Monitors
  │     └── Users: Charlie (Admin), Dave (Member)
  │
  └── MSP Client: Acme Corp
        ├── Acme Production Stack
        ├── Acme Staging Stack
        └── Users: Acme User (Viewer)

Creating Teams

Navigate to Teams

Go to Settings → Teams in the sidebar

Create New Team

Click “Create Team” button

Configure Team

Fill in team details:

Team Name: Engineering
Description: Engineering team's monitoring
Color: Blue (for visual identification)

Invite Members

Add team members with roles:

Admin - Full team management
Member - Create/edit resources
Viewer - Read-only access

User Roles & Permissions

StatusStack has two levels of roles:

Organization-Level Roles

Role	Permissions	Use Case
Owner	Full access to everything including billing	Company owner/founder
Admin	Manage teams, users, and all resources	IT director, CTO
Member	Create and manage resources within assigned teams	Engineers, operators

Team-Level Roles

Role	Permissions	Use Case
Team Admin	Full access within the team	Team lead, project manager
Team Member	Create/edit Stacks, Monitors, Notifications	Engineers, developers
Team Viewer	Read-only access to team resources	Stakeholders, clients (MSP)

Permission Matrix

Action	Owner	Org Admin	Org Member	Team Admin	Team Member	Team Viewer
Manage billing	✅	❌	❌	❌	❌	❌
Create teams	✅	✅	❌	❌	❌	❌
Delete teams	✅	✅	❌	❌	❌	❌
Invite org users	✅	✅	❌	❌	❌	❌
Invite team users	✅	✅	❌	✅	❌	❌
Create Stacks	✅	✅	✅*	✅	✅	❌
Delete Stacks	✅	✅	✅*	✅	✅	❌
View Stacks	✅	✅	✅*	✅	✅	✅
Create Monitors	✅	✅	✅*	✅	✅	❌
Configure Notifications	✅	✅	✅*	✅	✅	❌
View Analytics	✅	✅	✅*	✅	✅	✅

*Only within teams they’re a member of

Team Management

Inviting Team Members

Via Dashboard
Bulk Invite

Navigate to Settings → Teams
Select the team
Click “Invite Member”
Enter email address
Select role (Admin, Member, Viewer)
Send invitation

Managing Team Members

Change Role:

Go to team settings
Find user in members list
Click role dropdown
Select new role

Remove Member:

Go to team settings
Find user in members list
Click “Remove” button
Confirm removal

Transfer Ownership:

Organization Owner only
Go to organization settings
Click “Transfer Ownership”
Select new owner
Confirm transfer

Multi-Team Workflows

Scenario 1: Department-Based Teams

Organize by company departments:

Acme Corp Organization
  ├── Engineering Team
  │     ├── Production API Stack
  │     ├── Staging API Stack
  │     └── Development Stack
  │
  ├── DevOps Team
  │     ├── Infrastructure Stack
  │     ├── Database Stack
  │     └── CDN Stack
  │
  └── Support Team
        ├── Customer Services Stack
        └── Help Desk Stack

Benefits:

Clear ownership and responsibility
Department-specific monitoring
Targeted notifications per team

Scenario 2: Environment-Based Teams

Organize by deployment environment:

SaaS Startup Organization
  ├── Production Team
  │     ├── Prod API Stack
  │     ├── Prod Database Stack
  │     └── Users: On-call engineers
  │
  ├── Staging Team
  │     ├── Staging Stack
  │     └── Users: All engineers
  │
  └── Development Team
        └── Dev Stack

Benefits:

Environment isolation
Role-based access per environment
Separate notification rules

Scenario 3: MSP Client Teams

Managed Service Providers managing multiple clients:

MSP Company Organization
  ├── Internal Operations Team
  │     └── MSP Infrastructure Stack
  │
  ├── Client: Acme Corp Team
  │     ├── Acme Production Stack
  │     ├── Acme Staging Stack
  │     └── Users: Acme stakeholders (Viewers)
  │
  ├── Client: Beta Inc Team
  │     ├── Beta Production Stack
  │     └── Users: Beta stakeholders (Viewers)
  │
  └── Client: Gamma LLC Team
        └── Gamma Stack

Benefits:

Complete client isolation
Client-specific branding
Client portal access
Per-client billing

See MSP Setup Guide for detailed MSP workflows.

Access Control Best Practices

Principle of Least Privilege

Start restrictive, expand as needed

New users → Viewer role initially
Promoted to Member after training
Only trusted users get Admin role
Limit Organization Owners to 1-2 people

Team Separation

Keep teams focused

Production teams separate from development
Client teams isolated from each other (MSP)
Clear ownership of Stacks and Monitors

Regular Access Review

Quarterly access audit

Review active users
Remove users who left company
Verify roles are appropriate
Update team memberships

Secure Invitations

Invitation hygiene

Use company email addresses only
Set expiration on invitations
Verify identity before granting access
Use 2FA for sensitive teams

Organization Limits by Plan

Resource	Free	Pro	Enterprise
Organizations	1	1	Unlimited
Teams per Org	1	5	Unlimited
Users per Org	3	25	Unlimited
Users per Team	3	Unlimited	Unlimited
Stacks per Team	1	10	Unlimited

MSP-Specific Features

Client Portal Access

Grant clients view-only access to their monitoring:

Create a team for the client
Invite client users with Viewer role
Client users can:
- View their Stack status
- See incident history
- Subscribe to email updates
- Access public status pages
Client users cannot:
- Modify Stacks or Monitors
- Access other clients’ data
- View billing information
- Change notification settings

Client Branding

Customize per-client branding:

Custom Logos - Upload client logo for their team
Custom Colors - Match client brand colors
Custom Domains - status.clientdomain.com
White-Label - Hide StatusStack branding (Enterprise)

See MSP Branding Guide for details.

Common Scenarios

Adding a New Employee

Create User Account

Organization Admin invites user to Organization

Assign to Teams

Add user to appropriate teams (Engineering, Operations, etc.)

Set Team Roles

Assign role in each team (typically start with Viewer or Member)

User Accepts Invite

User clicks invitation link and creates account

Offboarding an Employee

Remove from Teams

Remove user from all teams in organization

Revoke Access

User automatically loses access to all resources

Audit Changes

Review any resources the user created or modified

Transfer Ownership

If user owned Stacks/Monitors, transfer to another user

Adding a New Client (MSP)

Create Client Team

Create a new team for the client: “Client: Acme Corp”

Set Up Stacks

Create client-specific Stacks within the team

Invite Client Users

Invite client stakeholders with Viewer role

Configure Branding

Customize logo, colors, and domain for client

Share Status Page

Provide client with their branded status page URL

Troubleshooting

User Can’t Access a Stack

Check:

User is member of the correct team
Stack belongs to that team
User has at least Viewer role
User accepted team invitation

User Can’t Create Resources

Possible Causes:

User has Viewer role (read-only)
Organization quota reached (upgrade plan)
User not member of any team

Invitation Not Received

Solutions:

Check spam/junk folder
Verify email address is correct
Resend invitation
Try different email provider

Next Steps

MSP Setup Guide

Configure multi-client monitoring

Team Management

Detailed team management documentation

User Roles

Security and access control

Subscription Plans

Compare plans and features

​Overview

​Organizations

​What is an Organization?

Single Tenant

Subscription Billing

Teams Management

Shared Resources

​Organization Settings

​Teams

​What are Teams?

​Team Hierarchy

​Creating Teams

​User Roles & Permissions

​Organization-Level Roles

​Team-Level Roles

​Permission Matrix

​Team Management

​Inviting Team Members

​Managing Team Members

​Multi-Team Workflows

​Scenario 1: Department-Based Teams

​Scenario 2: Environment-Based Teams

​Scenario 3: MSP Client Teams

​Access Control Best Practices

​Organization Limits by Plan

​MSP-Specific Features

​Client Portal Access

​Client Branding

​Common Scenarios

​Adding a New Employee

​Offboarding an Employee

​Adding a New Client (MSP)

​Troubleshooting

​User Can’t Access a Stack

​User Can’t Create Resources

​Invitation Not Received

​Next Steps

MSP Setup Guide

Team Management

User Roles

Subscription Plans

Overview

Organizations

What is an Organization?

Organization Settings

Teams

What are Teams?

Team Hierarchy

Creating Teams

User Roles & Permissions

Organization-Level Roles

Team-Level Roles

Permission Matrix

Team Management

Inviting Team Members

Managing Team Members

Multi-Team Workflows

Scenario 1: Department-Based Teams

Scenario 2: Environment-Based Teams

Scenario 3: MSP Client Teams

Access Control Best Practices

Organization Limits by Plan

MSP-Specific Features

Client Portal Access

Client Branding

Common Scenarios

Adding a New Employee

Offboarding an Employee

Adding a New Client (MSP)

Troubleshooting

User Can’t Access a Stack

User Can’t Create Resources

Invitation Not Received

Next Steps