Sharing and organizations

You can let other daemonitor accounts see your systems without handing over your login. A share grant gives one person access to your whole account, to one system, or to one group of services, with either a viewer or a manager role. Organizations are a second way in. They group systems by customer and give the organization's members access to those systems.

The systems stay yours in every case. Sharing never transfers ownership, and the system keys stay with you.

Share grants

What you can share

Scope	Gives access to	Where to set it
Whole account	Every system and group you own, including ones you add later	Settings, Delegation
One system	That system, all its services, their history and events	The system page, Share
One group	Only the services in that group, plus the names of the systems they run on	API only for now

A group share is the narrow one. The grantee sees the services in the group and nothing else on those hosts. They can't read the rest of a system's services or its history.

Roles

	Viewer	Manager
See the shared systems, services, history and events	yes	yes
Read incidents filed against those systems	yes	yes
Archive systems and services	no	yes
Create, edit and delete groups	no	yes, on a shared group, or anywhere in the account with a whole-account grant
Write and edit incidents	no	whole-account grant only
Rename the shared account's display name	no	whole-account grant only
Receive Slack alerts	no	whole-account or system grant

Neither role can delete systems, share them onward, assign them to an organization, or create enrollment tokens for them. Those stay with the owner.

Notifications explains exactly who gets paged.

Invite someone

Enter the person's email address and pick a role. What happens next depends on whether they have an account.

• If the email already has a daemonitor account, the grant is active at once.
• If not, the grant shows as "pending, awaiting sign-up". It activates by itself when someone signs up with that email.

You can't share with your own email address. Sharing the same thing with the same email again updates the role on the existing grant.

What the grantee sees

A whole-account grant adds your account to the grantee's account switcher. They view your fleet as you see it, without signing in as you. A system or group grant shows up in their fleet next to their own systems, marked as shared.

Change or remove a grant

The same share control lists every grant with its status. Change the role there, or remove the grant. Removal takes effect on the grantee's next request.

Organizations

An organization is a customer. It has a name, a colour, a description and a website, and a list of members. Assigning a system to an organization gives every member of that organization read access to the system.

This is meant for agencies and managed service providers. You keep owning your customers' systems and assign each one to the customer's organization. You can then:

• Keep the organization to yourself, purely to sort systems by customer.
• Invite a technical contact at the customer. They see that organization's systems and nothing else, because they own nothing and hold no share grants.
• Issue an organization-scoped API key that returns only that customer's systems.

Membership in one organization never reaches a system in another, or a system with no organization.

Create and manage an organization

Settings, Organizations. Whoever creates an organization becomes its owner.

Role	Can
owner	Everything an admin can, plus grant the owner role.
admin	Edit the profile, add and remove members, change roles.
member	See the organization, its member list, and the systems assigned to it.

Members must already have a daemonitor account. Unlike share grants, there are no pending invites. The last owner can't leave or be removed. Promote someone else first.

Assign a system

On the system page, choose an organization from the manage menu, or No organization to clear it. Only the system's owner can do this, and only to an organization they belong to.

Assigning a system is a sharing action. If the organization has other members, the dashboard asks you to confirm, and names how many people will gain access. Clearing the organization removes that access from members who have no other way in.

Organization members can read assigned systems. They are not paged for them, and they can't change them.