Sharing and who can open what
Every app starts private: only its owner and the people it is shared with can open it. An owner widens that from the app's Access page.
Who can open it#
Three levels of visibility:
- Private — only the owner and people it is shared with by email.
- Everyone in the org — anyone signed in at the owning organisation.
- Anyone with the link — anyone at all, signed in or not.
Roles on an app#
Sharing an app names someone as an editor or a viewer:
- Owner — can view it, deploy it, and everything administrative on top: change who can open it, share and unshare, transfer it, move it to another org, delete it.
- Editor — can view it and deploy it. Cannot change who can open it, share it, transfer it, move it, or delete it.
- Viewer — can view it. Nothing else.
Org roles#
An organisation has owners, admins and members. An org's owners and admins each count as an owner of every app in that org, whether or not anyone shared it with them by name — so putting an app in an org puts it within reach of whoever administers that org. A plain member gets no standing role on an app unless it is shared with them, except that an org-visible app is readable by every member; reading it grants no right to change or deploy it.
Sharing before someone has signed in#
Sharing works even for a colleague who has never used wirl: the invitation waits for their first sign-in and is theirs the moment they arrive.
Transfer and move#
npx wirl transfer dana@company.com
Hands the app to a new owner. You keep editor access.
npx wirl move --to acme
Moves the app to another organisation you belong to.
Where this lives in the dashboard#
An app's Access page holds its visibility setting, the people it is shared with and their roles, and the share form. Its Settings page holds the transfer form and, once you belong to more than one organisation, the move form. Both are visible only to someone who administers the app. An organisation's Members page is its roster: who belongs, their role, and a form to change either.