Docs / Getting Started

Invite Developers and Collaborators

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.

  1. You can sign in to https://my.looky.studio.
  2. CLI login and billing context are confirmed.
  3. A workspace exists and looky validate runs cleanly.
  4. 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

  1. Create and send invitation with explicit scope in the message.
  2. 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>
  3. Have the developer enter one assigned workspace and run:
    cd <local_root>/<billing_account_id>/<workspace_slug>
    looky status
    looky validate
  4. 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.