Portal

The Flitz portal at app.flitz.dev is where your organization looks back at what it has published, by app and track, and manages its apps, and where its Owner and Admins manage the organization: who can download each app's builds, the CI API key, single sign-on, members, and billing.

Sign in

Open app.flitz.dev. It sends you to sign in with the same Flitz account you use for flitz login, then opens on Publishes. The sidebar shows your organization, your email address, and Sign out.

An account that belongs to no organization lands on You're signed in — without an organization. Ask your organization's Owner or an Admin to invite that email address from Members.

Roles

Every member holds one of three roles. Each organization has exactly one Owner.

Nobody can remove the Owner or change the Owner's role. A Member sees Settings and Members read-only, with a note saying the Owner or an Admin makes changes. On an app's page a Member sees who can download its builds but cannot change it.

Publishes

The history of every flitz publish in the organization, newest first, with the columns App, Track, Version, Name, State, Published, By, and Links. App and Track open their pages; Links opens the landing page.

• The list shows Complete publishes. Tick Show incomplete publishes to add Pending ones (still uploading) and Abandoned ones (not finished within an hour). Neither has a working link yet: their Links cell reads Available when complete or Never completed.
• The App picker above the list filters it by app, and once an app is picked a Track picker filters by one of its tracks; All apps and All tracks clear them. Publishes of archived apps are listed; a deleted app's are not.
• Publishes load 50 at a time; Load 50 more fetches the next page.
• By names the member who published, or CI · org key for a publish made with the organization's API key.
• The name, version label, and comment come from flitz publish --name, --version-name, and --comment. See flitz publish.

Select a publish to open its detail: its app and track (each opens its page), name, app version, version label, comment, who published it, and when. A complete publish also shows a QR code of its flitz:// deeplink and an Open landing page button.

Delete publish removes a publish in any state. It leaves the history, its links and QR code stop working, and nothing restores it. If it was its track's newest build, the track's link moves to the previous complete one. Any member can delete a publish.

A publish's links work as long as the publish and its app exist, and who can download through them depends on the app's download access — see Links.

The same history is in the terminal: flitz publishes lists complete and pending publishes, --all adds abandoned ones, --app and --track filter them, and flitz publishes delete deletes one.

Apps

Apps shows your organization's publishes by app and track. For how a publish gets its app and track, see Apps and tracks. Pro includes one app; more than one app is part of Flitz Enterprise.

• The list shows each app's name, key, number of tracks, and last publish. Show archived apps adds archived ones, marked Archived. An app whose builds only members can download is marked Members only.
• An app's page shows its key, who can download its builds, and All publishes, which opens its history on Publishes. Below are its tracks, the most recently published first. Each track shows its latest publish and a Latest link to the track's page, which always opens the newest build on that track; QR shows that link as a QR code. Publishes made without a branch land on the Unassigned track.
• A track's page shows its latest link, its QR code, and its publishes.

Any member can manage an app from its page, and each action asks for confirmation first: Rename changes the display name, the key, or both; Archive and Unarchive stop and resume new publishes; Delete moves the app to the Deleted section at the bottom of Apps, which shows the time left, and Restore brings it back within 30 days. A key another app holds is refused. For what each action does to the app's tracks, publishes, and links, see Archive, delete, and restore. The same actions are in the terminal: flitz apps.

Download access

An app's page shows who can download its builds: Anyone with the link (the default for every app) or Members only, an Enterprise feature. The Owner and Admins change it with Download access (Who can download this app's builds); a Member sees it but cannot change it, and the CLI cannot change it. The setting covers every publish of the app, links already shared included, and the app's track links, from the next download. Members only builds open only in a host with sign-in. For what each setting means in a browser and on a device, see Download access.

Settings

Organization API key

The organization's one CI key, which pipelines present as FLITZ_APIKEY. The section shows the key obfuscated, when it was created, and when it was last used.

Owners and Admins can Create key when none exists, and Rotate or Revoke an existing one. Create and rotate show the new value once. Store it before you dismiss the dialog, because it can't be recovered afterwards. Rotating stops the old key the moment the new one is minted, and revoking cuts off every pipeline immediately.

The flitz apikey commands manage the same key from the terminal. There, create, rotate, and revoke are open to any member signed in with flitz login, not only the Owner and Admins.

Single sign-on

Shows whether SSO is configured, and each connection's name, provider, state, and creation date. A connection that is not active yet reads Not yet usable for sign-in. Owners and Admins open the SSO setup for your identity provider with Configure SSO, or Manage SSO once a connection exists.

Members

The page has two tabs.

• Members lists each person's name, email, role, last sign-in, and join date. Owners and Admins can Remove a member they outrank, and the Owner can Make Admin or Make Member. A removed member loses access to the organization's publishes and settings. The publish records they created stay, still attributed to them.
• Invitations invites a person by email address with a role, Member or, for the Owner, Admin, through Send invitation. The list shows each invitation's status (Pending, Accepted, Expired, or Revoked) and a Revoke action on pending ones.

Billing

Only the Owner sees Billing. The organization's license follows its subscription. While the subscription is live, every member can download SDKs and loader plugins, publish, and use the portal.

• No active subscription is where a new organization starts. Subscribe opens a hosted checkout page, which collects a card. An organization's first subscription starts with a 30-day free trial, and the card is charged when the trial ends. A trial that ends with no card on file pauses the subscription, and the license with it.
• Free trial shows the trial's end date and the days left. Subscription shows the next renewal date, or the date a canceled subscription ends. Both show the payment method and price. Manage billing opens a hosted page for changing the card, reading invoices, and canceling.
• When a payment fails, the page warns you to update the card to keep publishing.
• Billing is arranged with Flitz replaces all of this for an organization billed by agreement. There is nothing to manage in the portal; questions go to the support address the page shows.

After checkout, the page reads Finishing your subscription for a few seconds and updates itself once the license is active.

When the license is inactive

When the subscription ends, lapses, or was never started:

• The Owner is sent to Billing from every page, and can subscribe again there. A renewed subscription carries no free trial.
• Everyone else sees <organization>'s access is inactive and is asked to contact the Owner. The sidebar marks the organization License inactive.
• Licensed CLI commands fail with your organization's Flitz license is not active (exit 3) and suggest asking the Owner to open Billing in the portal. See troubleshooting.
• Published bundles and landing pages keep working, and the organization's data stays intact. A host's panel shows Flitz is unavailable for your organization instead of your apps.