Sharing Services

:::meta author=Docs-Team updated=2026-09-03 tags=sharing,permissions,collaboration
:::

:::breadcrumb Docs > User Guide > Sharing Services
:::

:::reading-time
:::

Sharing lets a service owner grant a teammate — or an entire messenger group — scoped access to one service. A share is a bundle of permission rules: what the recipient may view, which lifecycle actions they may run, whether they can deploy, and how many deploys they may run per day. Everything is enforced by the backend, so a rule you did not grant simply does not happen. This page covers creating a share, the presets, the full rule catalog, per-member overrides, and what recipients experience.

:::toc
:::

Who can share, and with whom

Only the service owner can create a share — this is enforced at the model level. A share targets exactly one recipient: a contact (a single user) or a messenger group (all its members, with optional per-member overrides). The Share button on a service card opens the dialog in create mode; on the I shared scope, Rules reopens it in edit mode.

The recipient picker has two tabs — Groups and Contacts — each with a search field. Group rows show the title and member count; contact rows show the nickname or @username, and your selection appears as a removable chip. Empty states point you to the right place: "Join a group in Messenger first." or "Add contacts in Messenger."

Presets: the four starting points

Instead of ticking dozens of checkboxes, start from a preset. Selecting one fills the rule grid; any manual change clears the preset chip, so the dialog always reflects reality.

:::matrix
| Capability | Viewer | Operator | Developer | Ops |
| --- | --- | --- | --- | --- |
| View service, logs, deploy logs, metrics | ✓ | ✓ | ✓ | ✓ |
| Start / Stop / Restart / Rebuild | ✗ | ✓ | ✓ | ✓ |
| Add and edit own deploys, select, download | ✗ | ✗ | ✓ | ✓ |
| Use restricted shell | ✗ | ✗ | ✓ | ✓ |
| View DB credentials | ✗ | ✗ | ✗ | ✓ |
| Volume management, change network / config | ✗ | ✗ | ✗ | ✓ |
| Daily deploy limit | 0 | 10 | 20 | 50 |
:::

[!NOTE] Two actions are never shareable at any preset: deleting the service and transferring ownership. They stay with the owner by design.

The rules in detail

Below the presets, the dialog offers the switches that fine-tune the share. The catalog, in the dialog's own wording:

| Group | Rules |
| --- | --- |
| Visibility | View service · View service logs · View deploy logs · View metrics · View DB credentials |
| Lifecycle | Start · Stop · Restart · Rebuild · Purge runtime |
| Deploys | Add deploy · Edit own deploys · Remove own deploys · Select active deploy · Download deploy zip · Edit others' deploys · Delete others' deploys |
| Volumes | Add volume · Edit volume · Delete volume · Attach volume · Detach volume |
| Infrastructure | Change network · Change service config · Use restricted service shell |

Two backend-only rules exist beyond the checkboxes — replacing another user's active shell session, and using advanced interactive shell tools — granted by the sharer through the API or group-panel flows when needed.

:::steps
• Open the dialog
Press Share on your service card.
• Choose the recipient
Pick a group or a contact from the two tabs.
• Pick a preset and adjust
Start from Viewer, Operator, Developer, or Ops, then toggle individual rules.
• Set the guardrails
Optional expiry, an admin-only gate, a note, and the Daily deploy limit (max 50).
• Share
Press Share; the recipient sees the service under their Shared with me scope immediately.
:::