Skip to content

Roles and permissions

What you can see and change on an organization’s observatories, telescopes, devices, observing accounts and observations comes from the roles you hold in that organization. This page lists the roles and, area by area, what each one allows. For what organizations, members and groups are, see People, organizations and groups.

  • Organization roles are the only source of authority over what an organization owns. A role applies to everything the organization owns: every observatory, every telescope and every device. There are no per-observatory or per-telescope roles, so you cannot limit a member to one telescope.
  • Roles add up. A member can hold several roles, and holds the union of what they allow. A member with no role beyond membership can see the organization’s profile and the observations they have access to for other reasons, and nothing of its hardware.
  • The set of roles is fixed. Every organization has the same seven roles; an organization cannot define its own.
  • Resources a person owns directly (a telescope or observing account owned by a user rather than an organization) are fully under that person’s control.
  • Some access does not come from roles. A telescope access grant gives an entity observing time, not authority over the telescope. Who may submit observations through an observing account is set by the account’s observing grants. An observation can be shared with named people and groups (see Sharing and access). The person who created an observation always keeps full rights over it.
  • A paired SkyNode holds manage rights on its own telescope and observatory (and on the devices there), so the node can create and update its devices, constraints and IP cameras without a person signing in each time.
  • Skynet staff create organizations, observatories and telescopes, and can act on an organization’s behalf when supporting it.

Assign roles on the organization’s People → Members page: the Manage roles button on a member’s row opens a dialog where you pick roles from Assign roles…. Roles can also be included in a personal invitation; a join link grants membership only.

Role In short
Owner Everything, including the organization’s settings and its owner role.
Device manager Runs the hardware: observatories, telescopes, devices, queues, access grants, manual control, operational notifications, the telescope application and the SkyNode installers.
Telescope viewer Read-only view of the hardware: the telescope and observatory pages and the frames the telescopes captured.
Observing manager The organization’s observing accounts and the observations they fund.
Membership manager Members and invitations.
Group manager The organization’s groups.
Member Nothing beyond membership.

Role changes are bounded: you can only grant or revoke roles whose permissions you hold yourself, so a membership manager can hand out Member and Membership manager, and only an owner can make someone an owner. Nobody below owner can change their own roles, and the organization’s last owner cannot be removed or demoted until someone else holds the owner role.

Each table lists who can take an action. “Owner, device manager” means a member needs at least one of those roles.

Action Who can
Edit the profile (name, short name, description, location, country, website, photo), Visibility and Member list on Settings → Profile Owner
Manage Settings → Alerts and Settings → Observing Policies Owner
Manage operational notification rules (Settings → Notifications, and the Notifications panel on a telescope’s Overview); see Operations notifications Owner, device manager
See Settings → Storage Owner, observing manager
Submit and follow telescope applications (Settings → Telescope Application) Owner, device manager
Download SkyNode, SkyCanary and SkyDesk (Settings → Software, shown once the organization owns a telescope); see Software downloads Owner, device manager
Action Who can
See People → Members and People → Invitations Owner, membership manager
Invite people, change members’ roles, remove members Owner, membership manager (within the limits above)
See all groups, create, edit and delete groups, and manage any group’s members Owner, group manager
Invite someone into a group Owner, membership manager, group manager
Manage one group’s members That group’s maintainers, plus the roles above

Ordinary members can see the member roster through the API while the organization’s Member list setting allows it; the website’s People pages are for the roles above.

Action Who can
See the organization’s observatories (the Observatories tab, and each observatory’s Overview, Live and IP Cameras) Owner, device manager, telescope viewer
Upload the observatory photo on its Overview, and edit the observatory through PATCH /v1/observatories/{uid} Owner, device manager
Create an observatory or site Skynet staff
Action Who can
Open the telescope pages: Overview, Live, Weather, IP Cameras, Queues, Access Grants, Schedule, Log, Reports, and Settings read-only Owner, device manager, telescope viewer
See the telescope’s tasks and schedule, including other observers’ observation names, and download the frames the telescope captured (raw, preview and thumbnail) Owner, device manager, telescope viewer
Edit Settings (identity, photo, location, Publicly listed, Available for scheduling) and the mount, enclosure and radio settings through the API Owner, device manager
Edit and reorder observing queues Owner, device manager
Issue, edit, reorder and revoke telescope access grants and queue access grants Owner, device manager
See and revoke the SkyNode installation tokens on API Tokens Owner, device manager
Open the telescope console (Manual control on the Live tab), take the telescope’s manual-control lease and send manual commands Owner, device manager
Create or delete a telescope Skynet staff

Frames are the exception to observation permissions on purpose: anyone who can view a telescope can check focus, tracking and flats on everything it captured. Pipeline products (calibrated frames, stacks), an observation’s own page, its results and its funding stay with the observation’s permissions, so a device manager or telescope viewer does not get those from their role.

Action Who can
See devices and instruments Owner, device manager, telescope viewer
Create, edit and delete devices, and create instruments, through the API Owner, device manager
Watch an IP camera Anyone who can view its telescope or observatory, or anyone at all when the camera and its parent are public
Change an IP camera’s owner settings, issue its publish credentials, delete it Owner, device manager
Take an IP camera’s control lease (pan, tilt, zoom, IR light) Owner, device manager
Edit or delete operational constraints and shutdown interlocks Owner, device manager
Create operational constraints and shutdown interlocks through the API as a person Owner

In practice devices, operational constraints and shutdown locks are created by the paired SkyNode, which uses its own manage rights; see Set up your observatory and telescope. Camera control is covered in IP cameras and manual control in SkyNode.

Action Who can
Pair a SkyNode installation with a telescope or observatory (signing in during SkyNode’s node selection) Owner
See the paired installations on Settings → Software, and revoke an installation through the API Owner

Pairing needs the organization’s settings rights as well as manage rights on the observatory and telescope, which today only the owner role carries. See Installing SkyNode.

Action Who can
See and manage all of the organization’s observing accounts (the Observing Accounts tab) Owner, observing manager
See, edit and share all observations the organization owns (the ones its accounts funded) Owner, observing manager
Submit an observation through an organization account Whoever holds one of the account’s observing grants, whatever their role

An organization is public by default: it is listed in the directory and shows its full profile. An owner can untick Visibility on Settings → Profile to make it unlisted. An unlisted organization is still reachable by direct link and still shows up as the owner of its public telescopes and observations, but anyone who is not a member sees only a minimal card: its name, slug and photo. Its description, short name, location, country, website, member count and observing policies are withheld. Members (and anyone holding a role in it) see the full profile.

The Member list setting on the same page decides whether ordinary members can see who else belongs to the organization; membership managers and owners always can.

The role names and the permission strings each one expands to are returned by GET /v1/organizations/{slug}/roles; they are the same for every organization.

Role Permission strings
owner all of the strings below, plus operational_constraint.view_all, operational_constraint.manage_all, settings.view, settings.manage
device_manager observatory.view_all, observatory.manage_all, telescope.view_all, telescope.manage_all, device.view_all, device.manage_all, notifications.manage
telescope_viewer observatory.view_all, telescope.view_all, device.view_all
observing_manager observation.view_all, observation.manage_all, observing_account.view_all, observing_account.manage_all
membership_manager membership.view, membership.manage
group_manager group.view_all, group.manage_all
member none

On a single telescope, telescope.manage_all becomes full rights (telescope.manage, which includes editing, queues and tasks), and telescope.view_all becomes view rights on the telescope, its queues and its tasks. Observatory and device permissions follow the same pattern, and an IP camera’s permissions are those on its telescope or observatory.