Skip to main content

​
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:
1

Navigate to Settings

Click Settings → Organization in the sidebar
2

Update Details

Configure Organization information:
  • Organization Name
  • Company Website
  • Contact Email
  • Time Zone
  • Logo (for branding)
3

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

1

Navigate to Teams

Go to Settings → Teams in the sidebar
2

Create New Team

Click “Create Team” button
3

Configure Team

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

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

RolePermissionsUse Case
OwnerFull access to everything including billingCompany owner/founder
AdminManage teams, users, and all resourcesIT director, CTO
MemberCreate and manage resources within assigned teamsEngineers, operators

​
Team-Level Roles

RolePermissionsUse Case
Team AdminFull access within the teamTeam lead, project manager
Team MemberCreate/edit Stacks, Monitors, NotificationsEngineers, developers
Team ViewerRead-only access to team resourcesStakeholders, clients (MSP)

​
Permission Matrix

ActionOwnerOrg AdminOrg MemberTeam AdminTeam MemberTeam 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

  1. Navigate to Settings → Teams
  2. Select the team
  3. Click “Invite Member”
  4. Enter email address
  5. Select role (Admin, Member, Viewer)
  6. Send invitation

​
Managing Team Members

Change Role:
  1. Go to team settings
  2. Find user in members list
  3. Click role dropdown
  4. Select new role
Remove Member:
  1. Go to team settings
  2. Find user in members list
  3. Click “Remove” button
  4. Confirm removal
Transfer Ownership:
  1. Organization Owner only
  2. Go to organization settings
  3. Click “Transfer Ownership”
  4. Select new owner
  5. 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

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
Keep teams focused
  • Production teams separate from development
  • Client teams isolated from each other (MSP)
  • Clear ownership of Stacks and Monitors
Quarterly access audit
  • Review active users
  • Remove users who left company
  • Verify roles are appropriate
  • Update team memberships
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

ResourceFreeProEnterprise
Organizations11Unlimited
Teams per Org15Unlimited
Users per Org325Unlimited
Users per Team3UnlimitedUnlimited
Stacks per Team110Unlimited

​
MSP-Specific Features

​
Client Portal Access

Grant clients view-only access to their monitoring:
  1. Create a team for the client
  2. Invite client users with Viewer role
  3. Client users can:
    • View their Stack status
    • See incident history
    • Subscribe to email updates
    • Access public status pages
  4. 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

1

Create User Account

Organization Admin invites user to Organization
2

Assign to Teams

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

Set Team Roles

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

User Accepts Invite

User clicks invitation link and creates account

​
Offboarding an Employee

1

Remove from Teams

Remove user from all teams in organization
2

Revoke Access

User automatically loses access to all resources
3

Audit Changes

Review any resources the user created or modified
4

Transfer Ownership

If user owned Stacks/Monitors, transfer to another user

​
Adding a New Client (MSP)

1

Create Client Team

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

Set Up Stacks

Create client-specific Stacks within the team
3

Invite Client Users

Invite client stakeholders with Viewer role
4

Configure Branding

Customize logo, colors, and domain for client
5

Share Status Page

Provide client with their branded status page URL

​
Troubleshooting

​
User Can’t Access a Stack

Check:
  1. User is member of the correct team
  2. Stack belongs to that team
  3. User has at least Viewer role
  4. User accepted team invitation

​
User Can’t Create Resources

Possible Causes:
  1. User has Viewer role (read-only)
  2. Organization quota reached (upgrade plan)
  3. User not member of any team

​
Invitation Not Received

Solutions:
  1. Check spam/junk folder
  2. Verify email address is correct
  3. Resend invitation
  4. 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