Skip to content

People, organizations and groups

Every observatory, telescope, observing account, observation, and access grant in Skynet is owned by an entity. As a telescope owner you’ll work primarily with two entity types — users and organizations — plus groups, which are how organizations partition their members.

Knowing how these fit together up front saves friction later: most of the access-control questions (“who can edit this queue?”, “whose observing account funded this observation?”) resolve back to the entity graph.

A user is one person (or one automated agent) interacting with Skynet. Users can:

  • Own observatories, telescopes, devices, and observing accounts directly (typical for single-owner amateur or research installations). Instruments belong to their telescope rather than to an owner.
  • Submit observation requests and access their results.
  • Hold memberships in one or more organizations and groups.
  • Hold direct access grants to telescopes and observing queues owned by others.

User accounts are created via the normal sign-up flow. A personal organization invitation is addressed to an email address: someone without an account signs up with that address, then accepts it.

An organization is the institutional owner — typically a university, research group, or observatory operator. Organizations exist to:

  • Own resources at institutional scale. University-owned telescopes and observatories live under the organization, not under any individual user. People come and go; the organization persists.
  • Manage membership. Organizations invite users, accept them as members, and revoke membership when needed. Invitations are emailed to a person, or shared as a join link: a URL (and QR code) anyone with it can use to join as a member until it expires, is revoked, or reaches its use limit — built for a workshop, a class, or a club meeting. Join links grant plain membership only; roles are assigned afterwards or through a personal invitation. (The API calls these open invitations: isOpen on the invitation record.)
  • Apply roles. Organizations assign members built-in roles that bundle permissions on resources the organization owns. The set of roles is fixed (below); an organization cannot define its own. Members hold one or more roles, which let you say things like “device managers can edit and control the telescopes, but only owners and observing managers can manage the observing accounts.”
  • Share telescope time with other organizations. There is no consortium record: an organization shares its telescopes with other users and organizations through telescope access grants and queue access grants, keeps ownership of its own facilities, and can adjust or revoke that access at any time.

For an organization-owned telescope, roles are what let you delegate day-to-day operations without handing out blanket admin rights.

Every organization has the same fixed set of roles: Owner, Device manager, Telescope viewer, Observing manager, Membership manager, Group manager and Member. Assign them to a member on the organization’s People page, or include them in a personal invitation; join links grant plain membership only. What each role can see and change is in Roles and permissions.

A group is a sub-collection of members inside an organization, used to grant access to a defined subset of people without naming each of them. Typical uses:

  • A class of students who all need access to a specific observing account for a semester.
  • A research team that shares a project’s observations. Every group member is also a member of the group’s organization. A group maintainer can add existing organization members directly; someone from outside the organization gets a group invitation instead, and accepting it adds them to both the organization and the group.

Groups have two roles of their own: maintainer (manages the group’s membership, observing accounts and observations) and member. The same person can therefore have different authority in different groups within the same organization.

Most resources in Skynet carry an ownerUid (the entity that owns it) and a collection of access grants (entities that have been granted specific permissions on it).

  • Observatories and telescopes are owned by an entity — usually an organization, sometimes a user. Owners have full administrative control.
  • Observing accounts are owned by an entity and aggregate one or more observing queues. Members can be granted permission to submit observations through the account.
  • Observations and projects are owned by the entity that funded them (so the bill lands in the right account). The creator is the user who actually authored the observation, which may differ from the owner when an org member submits on the org’s behalf.

For the specific telescope-side access surface — access grants, queues, queue access grants, observing accounts — see Telescope access.