Invite only after the first workspace works
Do not onboard more builders until at least one workspace is validated and pushable by the initial operator.
- You can sign in to
https://my.looky.studio. - CLI login and billing context are confirmed.
- A workspace exists and
looky validateruns cleanly. - At least one visualization/dashboard can be listed after push.
Permission model by job-to-be-done
Workspace access
Best default for most builders. Grants focused access to specific workspaces.
Billing developer
Use when someone must create/manage multiple workspaces under the billing account.
Owner-level invitation
Reserve for account operators, governance, and higher-risk admin actions.
Operational onboarding flow for each new developer
- Create and send invitation with explicit scope in the message.
- After acceptance, ask the developer to run:
looky login https://my.looky.studio <local_root> looky whoami cd <local_root> looky billing list looky billing use <billing_account_id> - Have the developer enter one assigned workspace and run:
cd <local_root>/<billing_account_id>/<workspace_slug> looky status looky validate - Confirm they can read dashboards in UI before asking for writes.
Use the narrowest role that still allows the work. This avoids accidental cross-workspace changes and keeps ownership clear.