Sharing and access
Every observation is restricted when it is created: only the people on its owner’s side can see it. From there, access widens in three deliberate ways: the observation is shared with named people or groups, it is made public, or an observing account that funds it lets its managers see it (sponsor view). This page explains each path and what a person who reaches the observation that way can do. For the steps in the website, see Share an observation.
Sharing is per observation. Projects cannot be shared with named people; a project is visible to anyone who can see one of its observations, or to everyone when it is public (see Projects).
Who can see an observation
Section titled “Who can see an observation”| Who | How they get access | What they can do |
|---|---|---|
| Owner | The user who owns the observation (for a personal observation). | Everything. |
| Creator | The user who submitted it, when that is not the owner (for example a member who submitted an organization-funded observation). | Everything the owner can. |
| Owning organization | Members holding the Owner or Observing manager role in the organization that owns the observation. | Everything. |
| Shared people and groups | Named on the observation as a Viewer or Editor, directly or as members of a group it is shared with. | Viewer: view and download. Editor: also change it. See Roles. |
| Sponsor accounts | Managers of an observing account above a delegated subaccount that funds the observation, when that account has sponsor view turned on. | View and download. See Sponsor view. |
| Everyone | The observation is public. | View, and download files one at a time without an account. |
The first three rows are the owner side. Being a member of an organization does not, by itself, let you see its observations: a member with no observing role sees the organization’s observations they created themselves, the ones shared with them, and the public ones. For what each organization role allows elsewhere, see People and organizations.
People who can view a telescope (its organization’s owners, device managers and telescope viewers) also see the frames that telescope captured, including other observers’, on the telescope’s own pages. That covers the captured frames only, not the observation’s page, results, processed products or funding.
Someone who cannot see an observation gets “not found”, never “forbidden”, so its existence is not revealed.
A share carries one of two roles. The owner side holds every right on the observation.
| Action | Owner side | Editor | Viewer, sponsor, public visitor |
|---|---|---|---|
| Open the observation, its results, images and files | Yes | Yes | Yes |
| Download files and packaged exports | Yes | Yes | Yes (packaged exports need a Skynet account) |
| Turn on notifications for it (the bell) | Yes | Yes | Yes, when signed in |
| See who has access (the Share dialog) | Yes | Yes | Yes, when signed in |
| Change its configuration, requests, target or processing settings; re-process; cancel or activate | Yes | Yes | No |
| Make it public or restricted | Yes | No | No |
| Share it, change a share, or remove one | Yes | No | No |
| Delete it | Yes | No | No |
| See which observing accounts and grants fund it | Yes | No | No |
Editor rights are enforced by the API. On the website, the observation page currently shows Edit, Cancel, Re-process data and the Processing controls only to the owner side, so an editor sees the page much as a viewer does and makes changes through the API.
The funding is the owner’s billing, not the science: anyone who reaches an observation by a share, by sponsor view or because it is public sees no funding on it (the Overview’s Observing accounts card has nothing to show them).
Public observations
Section titled “Public observations”A public observation can be viewed by anyone, signed in or not: its page, results and images, and its FITS files are downloadable one at a time. It may also appear on the owner’s public profile. Packaged downloads still need a Skynet account (see Download data).
You can make an observation public when you create it (the Public checkbox in the editor’s Configuration step) or later from the Share dialog. Only the owner side can change it. A deleted observation stops being public immediately.
Sharing with people and groups
Section titled “Sharing with people and groups”A share names one person or one group, with the role Viewer or Editor. Only the owner side can share; editors and viewers can see the list but not change it.
- People you can find. The search in the Share dialog finds people you share an organization with (in organizations where members can see each other, or where you can view the membership). Someone you find is added at once.
- Anyone else, by email. Type an email address that matches nobody you can find and Skynet emails an invitation. The person gets access when they accept it while signed in with that address (creating an account if they need one). An invitation expires; the dialog shows when, and resending it extends the deadline from the day you resend.
- Groups. An observation owned by an organization can be shared with that organization’s groups: those you belong to, or any of them if you are a group manager. Everyone in the group gets the role, and membership changes apply automatically. A personal observation cannot be shared with a group.
- Only additions. A share can only add access. Skynet refuses to share with someone who already has owner-side access (for example an observing manager of the owning organization), so the list always says where each person’s access really comes from.
- Ending a share. Removing a share takes effect immediately. The record is kept, marked as revoked, with who ended it and when. Revoking a pending invitation withdraws it.
- Deleting the observation withdraws every share.
People added directly are not notified. They find the observation on their own Observations page under Shared with me, or you can send them its link.
Sponsor view
Section titled “Sponsor view”When you give someone time through a delegated subaccount, the subaccount and everything submitted through it belong to them. You see the credits the branch uses, not their observations. Sponsor view is a setting on your observing account that changes the second part: with it on, anyone who can view your account (its personal owner, or for an organization’s account its owners and observing managers, plus the members of a bucket’s managing group) can also view the observations funded through the delegated subaccounts below it.
- View only. A sponsor can open the observation, its results and files, and download them. A sponsor cannot change anything, share it, or see its funding.
- What counts as funded. An observation counts when one of its funding grants sits on a delegated subaccount below your account, or when any of its tasks has been charged there. Taking the grant off an observation afterwards does not hide work your account already paid for. It is always the whole observation, not only the part one grant paid for.
- Any depth, each account for itself. For a chain A, then B, then C, A’s managers see C’s observations when A’s setting is on, whatever B chose. Buckets owned by the same owner do not count: their observations already belong to that owner.
- It applies to past observations too, and the account’s managers can turn it off at any time. An archived account’s setting has no effect.
- Not in lists. Sponsored observations do not appear in a sponsor’s observation lists or feeds. A sponsor finds them on the account and grant pages; see Sponsor observers.
- The grantee is told. A delegated subaccount’s page names every account above it with sponsor view on, and the observation’s Share dialog lists each such account as a view-only row for the owner side (never for someone the observation was merely shared with).
For developers
Section titled “For developers”The access list and the sharing calls are on the observation:
| Call | What it does | Who may call it |
|---|---|---|
GET /v1/observations/{uid}/access |
Who can see the observation and why: isPublic, canManage, and entries, each with a basis (owner, creator, organization, sponsor, grant, invitation) and a role. Invitations (which carry email addresses) are listed only to the owner side. |
Anyone who can view the observation |
POST /v1/observations/{uid}/access/grants |
Share with a person or a group as viewer or editor. |
Owner side |
PATCH /v1/observations/{uid}/access/grants/{grantUid} |
Change a share’s role. | Owner side |
DELETE /v1/observations/{uid}/access/grants/{grantUid} |
End a share. | Owner side |
POST /v1/observations/{uid}/access/invitations |
Invite by email. | Owner side |
POST …/access/invitations/{invitationUid}/resend, DELETE …/access/invitations/{invitationUid} |
Resend or revoke an invitation. | Owner side |
isPublic is set with PATCH /v1/observations/{uid}, which needs owner-side rights for that field. A scoped API token with observations:read can read the access list; no scoped token can change who has access. See the developer docs for tokens and scopes.