Workspaces & Teams
Manage multi-tenant workspaces, invite team members, and configure roles and permissions.
Workspaces are the top-level organizational unit in Ionhour. Everything — checks, projects, incidents, status pages, alert channels — belongs to a workspace. Each workspace has its own team, plan, and settings.
Creating a Workspace
Creating a workspace is a guided process with three steps, followed by an automated setup phase.
Name Your Workspace
Click Create Workspace from the workspace switcher or the workspaces page, then enter a name (e.g., your company or team name).
Invite Team Members
Optionally add team member email addresses. You can also skip this step and invite members later from workspace settings.
Choose a Plan
Select your workspace plan:
- Free — Get started with core monitoring features.
- Pro — Unlock higher limits, dependencies, deployments, and more. Includes a 14-day free trial with no charge upfront.
For paid plans, select a billing cycle (monthly or yearly).
After completing the wizard, a provisioning screen runs your setup tasks automatically:
- Setting up billing (paid plans only) — A checkout window opens to collect your payment method.
- Activating your workspace — Your workspace is created and configured.
- Sending team invitations — Invitation emails are sent to any addresses you provided.
- Finalizing setup — Final configuration and cleanup.
Each task shows its progress in real time. Once all tasks complete, click Go to your workspace to start monitoring.
You automatically become the Owner of workspaces you create.
Roles and Permissions
Every workspace member has a role that determines what they can do.
| Role | Access |
|---|---|
| Owner | Full control. Can delete the workspace, transfer ownership, and manage all members. |
| Admin | Can manage settings, team members (Member/Viewer only), and all operational features. Cannot modify other Admins or the Owner. |
| Member | Can create and manage checks, view incidents, and use all monitoring features. Cannot manage team or workspace settings. |
| Viewer | Read-only access. Can view checks, incidents, and dashboards but cannot make changes. |
Role Hierarchy
Admins can only change the role of Members and Viewers — they cannot modify other Admins or the Owner. Only the Owner can promote someone to Admin or demote an Admin.
The Owner role cannot be removed. To change the Owner, use the ownership transfer feature.
Inviting Team Members
Sending Invitations
Each invitee receives an email with a link to accept the invitation. Invitations expire after 7 days.
Invitation Lifecycle
| Status | Meaning |
|---|---|
| Pending | Invitation sent, waiting for response |
| Accepted | User accepted and joined the workspace |
| Rejected | User explicitly declined |
| Canceled | An Owner or Admin revoked the invitation |
| Expired | 7 days passed without a response |
You can resend a pending invitation (generates a new token and resets the expiry) or cancel it entirely.
Accepting an Invitation
When a user clicks the invitation link:
- If they already have a Ionhour account, they're prompted to accept or reject.
- If they don't have an account, they'll create one first, then accept.
- On acceptance, they're added to the workspace with the assigned role and redirected to the workspace dashboard.
If the invitation email doesn't match the signed-in account, the user is prompted to sign in with the correct account.
Managing Members
Changing Roles
- Go to Settings > Workspace > Team.
- Find the member in the list.
- Select a new role from the dropdown.
Role changes take effect immediately. Remember: Admins can only change Members and Viewers. Only the Owner can change Admin roles.
Removing Members
- Go to Settings > Workspace > Team.
- Click the remove action on the member you want to remove.
Removed members immediately lose access to the workspace. Their historical activity (created checks, incidents, notes) is preserved.
Transferring Ownership
The Owner can transfer workspace ownership to any existing member.
- Go to Settings > Workspace > Danger Zone.
- Click Transfer Ownership.
- Select the new owner from the member list.
- Confirm the transfer.
The transfer:
- Promotes the selected member to Owner.
- Demotes the current Owner to Admin.
- Is immediate and irreversible (without another transfer).
Deleting a Workspace
Only the Owner can delete a workspace.
- Go to Settings > Workspace > Danger Zone.
- Click Delete Workspace.
- Confirm the deletion.
Workspace Settings
General Settings
| Setting | Description |
|---|---|
| Name | The workspace display name (Owner and Admin can edit) |
| Plan | Current subscription plan (Free, Pro, Business) |
| Dependency Impact Alerts | Enable or disable dependency impact propagation for the workspace |
Feature Availability by Plan
Some features are gated by workspace plan. You can upgrade at any time from Settings > Billing.
| Feature | Free | Pro | Business |
|---|---|---|---|
| Team members | 1 | Multiple | Multiple |
| Dependency impact alerts | Limited | Full | Full |
| Check limits | Basic | Higher | Highest |
| Outbound check limits | Limited | More | Most |
Workspace-Scoped Data
All data in Ionhour is workspace-scoped. When you switch workspaces, you see a completely separate set of:
- Projects and checks
- Incidents
- Status pages
- Alert channels
- Dependencies
- Deployments
This multi-tenant model ensures complete isolation between workspaces. A user can be a member of multiple workspaces with different roles in each.
User Profile Settings
Some settings apply to your user account across all workspaces:
| Setting | Description |
|---|---|
| Timezone | Used for all date/time displays |
| Date format | How dates are formatted in the UI |
| Time format | 12-hour or 24-hour time |
| Email notifications | Global toggle for email alerts |
These are configured in Settings > Profile.
Best Practices
- Use the principle of least privilege. Assign Viewer roles to stakeholders who need visibility but shouldn't modify monitoring. Use Member for engineers who create and manage checks. Reserve Admin for team leads.
- Create separate workspaces for separate concerns. If you have completely independent products or teams that don't share infrastructure, separate workspaces provide cleaner isolation.
- Don't share a single workspace across unrelated teams. Workspace-level settings (alert channels, plans, dependency toggles) apply to everyone. Teams with different alerting needs should have their own workspaces.
Transfer ownership before the Owner leaves. If the Owner leaves your organization, you'll need support to recover the workspace. Transfer ownership proactively before any team changes.