Skip to main content

Add Team Members

Invite your team to NightOps so they can view infrastructure status, start/stop collections, and receive notifications.

Inviting Members

From the Dashboard

  1. Go to Team in the sidebar
  2. Click Invite Member
  3. Enter their email address
  4. Select their role (see Roles & Permissions)
  5. Click Send Invite

The invitee receives an email with a link to join your organization.

Bulk Invite

  1. Go to Team → Invite Member
  2. Click Bulk Invite
  3. Enter multiple email addresses (one per line):
    alice@company.com
    bob@company.com
    charlie@company.com
  4. Select the role for all invitees
  5. Click Send Invites

Member Roles

RoleDescription
OwnerFull access, can manage billing and delete org
AdminFull access except billing and org deletion
MemberCan view and control resources they have access to
ViewerRead-only access to resources

See Roles & Permissions for detailed permission matrix.


Pending Invites

View and manage pending invitations:

  1. Go to Team
  2. Click Pending Invites tab
  3. For each invite, you can:
    • Resend — Send another invitation email
    • Revoke — Cancel the invitation

Invitations expire after 7 days. Expired invites can be resent.


Member Settings

Edit Member

  1. Go to Team
  2. Click on a member's name
  3. Update their settings:
SettingDescription
Display NameHow they appear in the UI
RoleTheir permission level
TimezoneFor schedule displays and notifications
Notification PreferencesEmail/Slack notification settings

Change Role

  1. Go to Team
  2. Find the member
  3. Click the role dropdown
  4. Select new role
  5. Confirm the change
note

Only Owners and Admins can change member roles. You cannot change your own role.

Remove Member

  1. Go to Team
  2. Find the member
  3. Click Remove
  4. Confirm removal

Removed members immediately lose access. Their action history is preserved for audit purposes.


Collection Access

By default, Members can access all collections. To restrict access:

Grant Collection Access

  1. Go to Team → Member → Access
  2. Under Collection Access, click Add
  3. Select collections they can access
  4. Set permission level (View, Start, Stop, Edit)
  5. Save

Restrict to Specific Collections

  1. Go to Team → Member → Access
  2. Toggle Restrict to specific collections
  3. Add only the collections they should access
  4. Remove any they shouldn't

Example:

Alice (Backend Team)
├── Staging API ✓ Full Access
├── Staging Workers ✓ Full Access
├── Staging Database ✓ View Only
└── Production ✗ No Access

SSO Integration

For larger teams, integrate with your identity provider:

Google Workspace

  1. Go to Settings → Authentication
  2. Click Configure SSO
  3. Select Google Workspace
  4. Enter your Google Workspace domain
  5. Enable Auto-provision users

New users from your domain are automatically added as Members.

Okta

  1. Go to Settings → Authentication
  2. Click Configure SSO
  3. Select Okta
  4. Enter your Okta domain and credentials
  5. Map Okta groups to NightOps roles:
    okta-nightops-admins  → Admin
    okta-nightops-members → Member
    okta-nightops-viewers → Viewer

SAML 2.0

  1. Go to Settings → Authentication
  2. Click Configure SSO
  3. Select SAML 2.0
  4. Upload your IdP metadata XML or enter:
    • SSO URL
    • Entity ID
    • Certificate
  5. Configure attribute mappings

Notification Preferences

Each member can configure their notification preferences:

Email Notifications

NotificationDefaultDescription
Schedule executedOffWhen scheduled start/stop runs
Action failedOnWhen a start/stop operation fails
Weekly summaryOnWeekly cost and usage report

Slack Notifications

If Slack is connected, members can:

  1. Link their Slack account
  2. Receive DMs for personal notifications
  3. Choose which events trigger notifications

See Slack Integration for setup.


Activity Log

View what actions members have taken:

  1. Go to Team → Member
  2. Click Activity tab
  3. See recent actions:
    2024-01-15 10:30  Started collection "Staging API"
    2024-01-15 09:00 Stopped collection "Dev Environment"
    2024-01-14 18:00 Created schedule "Weekend Off"

Organization Activity

View all member activity:

  1. Go to Settings → Activity Log
  2. Filter by:
    • Member
    • Action type
    • Date range
    • Collection/Asset

Best Practices

Role Assignment

Team MemberRecommended Role
Engineering LeadAdmin
DevOps EngineerAdmin
Backend DeveloperMember (specific collections)
QA EngineerMember (QA collections only)
Product ManagerViewer
FinanceViewer (for cost visibility)

Collection Access

Production Collections
└── Admins only (no scheduled management)

Staging Collections
└── All engineers (full access)

Development Collections
└── Individual teams (their resources only)

QA Collections
└── QA team + relevant engineers

Onboarding Checklist

When adding a new team member:

  • Send invite with appropriate role
  • Grant access to relevant collections
  • Add to Slack channel (if using Slack integration)
  • Share documentation links
  • Schedule brief walkthrough

Troubleshooting

Invite Not Received

  1. Check spam/junk folder
  2. Verify email address is correct
  3. Resend the invitation
  4. Check if email domain is blocked by your mail server

Cannot Change Role

  • Only Owners and Admins can change roles
  • Cannot change your own role
  • Cannot demote the last Owner

SSO Login Failing

  1. Verify SSO is properly configured
  2. Check user exists in your IdP
  3. Verify group mappings are correct
  4. Check IdP logs for errors

Next Steps