> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livry.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Livry FAQ: Environments, Tokens, Signing, and Accounts

> Answers to common Livry questions about environment boundaries, schema-less tokens, signed URL authentication, passwordless sign-in, and plans.

<AccordionGroup>
  <Accordion title="Can I move an Organization from sandbox to live?">
    No. Organizations belong to exactly one Tenant and don't move between environments. If you need to mirror brand configuration into live, script it against the Management API as part of your own release process. See [Organizations and overrides](/theming/organizations).
  </Accordion>

  <Accordion title="Does Livry validate my token names?">
    No. Token documents are schema-less JSON, so Livry stores what you send without checking names against a vocabulary. Handle missing tokens defensively in your frontend. See [Tokens](/theming/tokens).
  </Accordion>

  <Accordion title="Why can't I use an API key for theme requests?">
    Theme fetches happen in the browser at volume and should be cacheable at the edge. Signed URLs can be computed server-side and handed to the client safely; a bearer token can't. See [Signed URLs](/serving/signed-urls).
  </Accordion>

  <Accordion title="I forgot my password.">
    Livry sign-in is passwordless — there is no password. Enter your email and follow the link Livry sends. If you've lost access to the email address itself, contact support.
  </Accordion>

  <Accordion title="Can one account belong to more than one Team?">
    Yes. Accounts and Teams are separate; switch between Teams inside the developer portal.
  </Accordion>

  <Accordion title="How do I get on the Enterprise plan?">
    Enterprise isn't self-serve. Get in touch and we'll scope a plan against your requirements. See [Billing](/settings/billing).
  </Accordion>
</AccordionGroup>