Telescope access
This page is the owner-facing model for who can observe with your telescope and how their time is prioritized. There are four things to know:
- Telescope ownership — who has full administrative control.
- Observing queues — the prioritized lanes that time on your telescope is divided into.
- Queue access grants — who can hold time on a given queue.
- Observing accounts — how those grants are bundled and presented to the people actually submitting observations.
Together these let you delegate time without delegating control, and share the telescope across audiences (institutional research, education, external collaborators, ToO follow-up) without conflating them.
New here, and someone just asked you for access? Skip to Three ways to grant someone access — the sections above define the pieces it refers back to. For the steps in the website, see Grant access.
Telescope ownership
Section titled “Telescope ownership”Telescopes are owned by an entity — either an organization or an individual user. The owner has full administrative control: configuration, queues, and who may observe. Inside an owning organization, that authority is handed out through organization roles, not per-telescope grants: the owner and device manager roles can manage every telescope the organization owns, and the telescope viewer role can see the telescope pages (overview, schedule, queues, reports) without changing anything. See Roles and permissions. Switching a telescope between computer-controlled and manual operation is done at the telescope, in SkyNode.
A TelescopeAccessGrant is not an operating permission: it admits a user or organization to observe with the telescope and carries their shares. See Telescope access grants.
Observing queues
Section titled “Observing queues”Each telescope carries an ordered list of observing queues. A queue is a named lane of time — a newly set-up telescope gets Maintenance, TOO (target of opportunity), Calibration, and General — and the order on the telescope is its priority order. No two queues share a position. The scheduler tries to satisfy higher queues first; lower queues fill remaining time.
Each queue has its own prioritization model, which orders the queue’s access grants:
- Fixed (shown as Default) — grant priorities you set by hand, as a strict list with one grantee per position; they don’t change as time is used. Best for fully manual allocation policies and ToO lanes.
- Fair-share (Total usage for telescope-wide, Queue usage for queue-local) — intended to adjust grant priorities so each grantee trends toward their
shares, measured on contested time only. Today the scheduler treats every grant in a fair-share queue as an equal peer; usage-based re-ranking is not live yet. - Calendar (Schedule-driven) — intended to let grant priorities follow a schedule of periods. Periods cannot be defined yet, and today the scheduler treats every grant in such a queue as an equal peer.
Queues are the right tool for coarse allocation policy (“ToO follow-up always goes ahead of general observing”); within a grantee’s slice of a queue, the grantee’s own account and grant levels take over. You never need a queue per grantee: each grantee already has the levels it needs inside its own observing accounts. The full ranking chain — queue level → grant level → root-account level → grant level at each account — is spelled out in Queue prioritization.
Queue access grants
Section titled “Queue access grants”An ObservingQueueAccessGrant says “this entity is allowed to put observations through this queue, at this position.” It hangs off the entity’s telescope access grant, which carries the entity’s shares. Grants can be issued to users or organizations, and they can be revoked at any time.
A queue without any access grants is reachable by nobody, the telescope owner included: the owner observes through its own telescope access grant and queue access grants like everyone else (the standard setup creates them). As you grant access, you build up the audience of the queue.
Observing accounts
Section titled “Observing accounts”An observing account is what observers see — the practical handle they submit observations against. Internally it’s a bundle of queue access grants — at most one per telescope, possibly spanning many telescopes — aggregated under a single owner. Picking an account is picking the lane on each telescope it reaches.
That layer exists for four reasons:
- Resource aggregation. A consortium with grants on five different telescopes can aggregate them into one observing account so its members don’t have to think about which queue to hit for each request — the scheduler picks among eligible telescopes.
- Permission delegation. The account’s owner controls who can submit observations through it. A research group lead can give submit-rights to their students without those students being personally grant-holders on the underlying queues.
- Quota throttling. Both the account and each grant under it can carry one or more quotas —
(period, max_credits)rules that cap how much can be spent within a window. Multiple quotas compose (a lifetime cap plus a rolling weekly cap, for example); all active quotas must be satisfied. This is where a parent grant can say “this delegated subaccount may not consume more than X per week” independently of the overall pool’s policy. - Prioritization within the grantee’s slice. An entity ranks its root accounts, and every account’s managers rank the account’s grants — rosters, members, buckets, and delegations in one ordered list — so an entity decides how its own slice of a queue divides under contention: research account ahead of outreach account, thesis students ahead of intro sections. Everything starts tied. None of this affects other grantees or your queue configuration; it only orders work inside the slice you granted. See Queue prioritization.
So the flow is: owner → grants → account → observer. The owner issues queue access grants to entities. Those entities create observing accounts that bundle their grants. Members of those entities submit observations through the accounts.
Three ways to grant someone access
Section titled “Three ways to grant someone access”Everything above is the machinery. In practice, when someone asks to observe with your telescope, you’re choosing between three routes — and the real difference between them is who ends up owning the observations, and how much oversight you keep.
| Route | The recipient gets… | Observations owned by | You keep control of | Best for |
|---|---|---|---|---|
| 1. Direct queue access | Time on your queue(s), plus the ability to create and run their own observing accounts | The recipient | The queue’s share and prioritization; revoking the grant | A partner or group you want running its own program |
| 2. Member grant on your observing account | Permission to submit through an observing account you own | You, the observing account’s owner | Everything — the observing account, its grants, quotas, and the observations | Programs you want to oversee and keep institutional |
| 3. Delegated grant on your observing account | An observing subaccount they own, funded from your allocation | The recipient | The delegation’s rank among your grants, a quota on it, and a revoke switch — nothing more | External collaborators who must own their own data |
The difference that matters is which side of the ownership boundary each route lands on — routes 1 and 3 cross into the recipient’s space, route 2 stays in yours:
flowchart LR
OWN["You — telescope owner"]:::owner
subgraph YOURS["Your org's space · your org owns the observations"]
direction TB
MEMBER["Member / group<br>in your org"]:::node
ACCT["Observing account<br>you own"]:::node
MEMBER -->|"Route 2 · Member grant"| ACCT
end
subgraph THEIRS["Recipient's space · the recipient owns the observations"]
direction TB
ROOT["Their own root<br>observing account"]:::node
SUB["A subaccount<br>they own"]:::node
end
OWN -->|"Route 1 · Queue access grant"| ROOT
OWN --> ACCT
ACCT -->|"Route 3 · Delegated grant"| SUB
classDef owner fill:#eaf7f0,stroke:#2e7d32,stroke-width:1.5
classDef node fill:#f8fafc,stroke:#94a3b8,stroke-width:1
style YOURS fill:#eaf7f0,stroke:#2e7d32,stroke-width:1
style THEIRS fill:#fff7ed,stroke:#ea580c,stroke-width:1
1. Give direct queue access
Section titled “1. Give direct queue access”The entity receives a TelescopeAccessGrant (with a number of shares) and one or more ObservingQueueAccessGrants. This puts time directly in their hands: a root account is only funded by queues its owner already holds grants for, so holding a queue access grant is what lets an entity stand up usable observing accounts of its own. From there the recipient is self-sufficient — they can bundle your queues with grants on other telescopes into a single account, add member grants for their own people, and delegate their own subaccounts to outside collaborators.
- You keep control of the allocation — their
shares, which queues they reach, and their position in each queue’s prioritization. (Fair-share enforcement ofsharesis not live yet; today a fair-share queue treats its grantees as equals.) - You give up visibility into individual observations; they belong to the recipient, in the recipient’s space.
- Reach for this when you want a collaborator to run their own program and manage their own people, and you only need to govern how much telescope time they get and at what priority.
Steps: Grant access → Give direct queue access.
2. Add them to an account you own (member grant)
Section titled “2. Add them to an account you own (member grant)”The person receives a MemberObservingGrant (or a whole group a GroupObservingGrant, or every org member an OwnerObservingGrant) on an observing account owned by your organization. They can then submit observations through the account — but the account, and everything submitted through it, stays owned by your organization. The member can’t pull that account into their personal space, and you retain the right to see, examine, and modify what they submit.
- You keep full oversight: you own the account, its grants, its quotas, and the observations themselves. Per-grant quotas let you cap each member independently.
- You give up nothing on the ownership side — but the member can’t take “their” observations with them; the data is institutional.
- Reach for this when the organization wants to run and be accountable for the observing — staff working under an institutional allocation, a PI’s students observing under the PI’s account, a class whose data the department retains.
Steps: Grant access → Add someone to an account you own.
Member and group grants are meant for people and groups inside your organization. To bring in someone outside your organization, use route 3.
3. Delegate a subaccount they own (delegated grant)
Section titled “3. Delegate a subaccount they own (delegated grant)”An external user or organization receives an ExternallyManagedObservingGrant (labeled Externally managed in the website) on an account you own. When they accept, Skynet creates a subaccount owned by them, hanging off your account. They see it in their own space and fully own everything they submit through it — the subaccount draws on the queues your parent account already exposes, but adds no new access of its own.
- You keep exactly four levers: set the delegation’s rank among your account’s grants, attach a quota to the delegation to cap how much they consume, revoke the delegation, or archive your own node. Credit usage still rolls up to you (so quotas work and you can watch aggregate consumption) — but the observations are theirs: you cannot modify them, and you can view them only if your account turns on sponsor view.
- You give up oversight of their individual observations. If you need to inspect or manage their data, that’s route 2, not this.
- Reach for this when an outside partner or consortium member must own their own data and manage their own people, while drawing time from your allocation under a spending cap you control.
Steps: Sponsor observers → Delegate a subaccount.
For the same slicing within your own organization — a class or lab that manages itself day-to-day while the data stays org-owned — create an internal bucket (
InternalObservingGrant) instead: the subaccount is owned by your organization, optionally managed by one of your groups, and ranked among your grants like any other.
The same tools at every level
Section titled “The same tools at every level”These routes aren’t mutually exclusive, and they compose. The moment you use route 1 to give an entity direct queue access, that entity gets the same three choices for its own members and partners — member grants inside its org, delegated subaccounts for outsiders. Access fans out down a tree, and at every node the owner governs only its own slice: share and priority above, ownership and oversight below.
In the web app
Section titled “In the web app”The step-by-step pages for owners:
- Grant access — admitting users and organizations on the telescope’s Access Grants tab, and member or delegated grants on observing accounts you own.
- Configure queues — the telescope’s Queues tab: queue order, prioritization, and the order of each queue’s access grants.
- Observing policy and shutdown interlocks — observing policies under the organization’s Settings → Observing Policies, plus constraints and interlocks in SkyNode.
Telescope access model
Section titled “Telescope access model”flowchart LR TEL["Telescope"] --> TAG["Telescope access grants<br/>one per admitted user or organization<br/>(shares, credits used)"] TEL --> QS["Queues, in strict order<br/>Maintenance → TOO → Calibration → General"] QS --> Q["Each queue<br/>prioritization: fixed · fair-share · calendar"] Q --> QAG["Queue access grants<br/>one per grantee per queue<br/>(level within the queue)"] TAG -. admits .-> QAG QAG --> ACC["Grantee's observing accounts<br/>at most one queue per telescope"]
Only fixed prioritization is live today; in fair-share and calendar queues every grant is an equal peer (see Implementation status).