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
- Go to Team in the sidebar
- Click Invite Member
- Enter their email address
- Select their role (see Roles & Permissions)
- Click Send Invite
The invitee receives an email with a link to join your organization.
Bulk Invite
- Go to Team → Invite Member
- Click Bulk Invite
- Enter multiple email addresses (one per line):
alice@company.com
bob@company.com
charlie@company.com - Select the role for all invitees
- Click Send Invites
Member Roles
| Role | Description |
|---|---|
| Owner | Full access, can manage billing and delete org |
| Admin | Full access except billing and org deletion |
| Member | Can view and control resources they have access to |
| Viewer | Read-only access to resources |
See Roles & Permissions for detailed permission matrix.
Pending Invites
View and manage pending invitations:
- Go to Team
- Click Pending Invites tab
- 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
- Go to Team
- Click on a member's name
- Update their settings:
| Setting | Description |
|---|---|
| Display Name | How they appear in the UI |
| Role | Their permission level |
| Timezone | For schedule displays and notifications |
| Notification Preferences | Email/Slack notification settings |
Change Role
- Go to Team
- Find the member
- Click the role dropdown
- Select new role
- Confirm the change
Only Owners and Admins can change member roles. You cannot change your own role.
Remove Member
- Go to Team
- Find the member
- Click Remove
- 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
- Go to Team → Member → Access
- Under Collection Access, click Add
- Select collections they can access
- Set permission level (View, Start, Stop, Edit)
- Save
Restrict to Specific Collections
- Go to Team → Member → Access
- Toggle Restrict to specific collections
- Add only the collections they should access
- 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
- Go to Settings → Authentication
- Click Configure SSO
- Select Google Workspace
- Enter your Google Workspace domain
- Enable Auto-provision users
New users from your domain are automatically added as Members.
Okta
- Go to Settings → Authentication
- Click Configure SSO
- Select Okta
- Enter your Okta domain and credentials
- Map Okta groups to NightOps roles:
okta-nightops-admins → Admin
okta-nightops-members → Member
okta-nightops-viewers → Viewer
SAML 2.0
- Go to Settings → Authentication
- Click Configure SSO
- Select SAML 2.0
- Upload your IdP metadata XML or enter:
- SSO URL
- Entity ID
- Certificate
- Configure attribute mappings
Notification Preferences
Each member can configure their notification preferences:
Email Notifications
| Notification | Default | Description |
|---|---|---|
| Schedule executed | Off | When scheduled start/stop runs |
| Action failed | On | When a start/stop operation fails |
| Weekly summary | On | Weekly cost and usage report |
Slack Notifications
If Slack is connected, members can:
- Link their Slack account
- Receive DMs for personal notifications
- Choose which events trigger notifications
See Slack Integration for setup.
Activity Log
View what actions members have taken:
- Go to Team → Member
- Click Activity tab
- 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:
- Go to Settings → Activity Log
- Filter by:
- Member
- Action type
- Date range
- Collection/Asset
Best Practices
Role Assignment
| Team Member | Recommended Role |
|---|---|
| Engineering Lead | Admin |
| DevOps Engineer | Admin |
| Backend Developer | Member (specific collections) |
| QA Engineer | Member (QA collections only) |
| Product Manager | Viewer |
| Finance | Viewer (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
- Check spam/junk folder
- Verify email address is correct
- Resend the invitation
- 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
- Verify SSO is properly configured
- Check user exists in your IdP
- Verify group mappings are correct
- Check IdP logs for errors
Next Steps
- Configure roles and permissions — Fine-tune access control
- Set up Slack integration — Let team control via Slack
- View schedule examples — Set up automated schedules