Hosted workspaces

Creating and using a workspace on a hosted installation.

On a hosted installation every team has its own workspace at its own address, such as your-team.albaticket.com. Workspaces are completely separate: users, projects, settings and data in one are invisible to the others.

Creating a workspace

The sign-up page is for the hosted service only: a workspace is Alba Ticket in our cloud. Running it on your own servers needs no sign-up, just the installation guide and, above the free size, a licence key from the licence portal. Open the sign-up page on the main site, choose a workspace name and address, and give your name and email. The page then tells you where the confirmation link was sent and what happens next; nothing is created until you follow that link, which works for 24 hours, and press Create the workspace on the page it opens. That creates the workspace with you as its administrator and logs you in. The first time you log in you are asked, once, what the workspace uses: every module is on, and the REST API, the MCP server, public request forms and iCloud calendars are off until you switch them on. All of it can be changed later under Modules and features. If no email arrives, check your spam folder, or use "Change the details and send again" on that page to correct the address. A workspace address that nobody has taken yet says so when you visit it, and offers to create the workspace with that address filled in. If the installation's operator has created a workspace for you instead, your first visit to its address shows a setup page that creates the administrator account.

Plan and billing

A hosted workspace starts on a 30-day trial with everything unlocked, and nobody is asked for a card to begin. Administration, Plan and billing shows where it stands: the plan and the number of members it is charged for.

When the trial ends, a workspace that is still small — within the free plan's limits on members, projects and attachments — simply becomes free, and is never asked for anything. One that has outgrown it carries a notice saying so, keeps working for thirty days, and says on the Plan and billing page which day that runs out.

After that the workspace becomes read-only: tickets, projects and boards can be read but not changed. Everything is still there, an export is always allowed, and an administrator can still manage accounts and settings — which is how you take a workspace back under the free plan if you would rather not pay. Choosing a plan, or dropping under the limits again, lifts it at once.

A seat is a member who has logged in during the last 30 days, and the seat is the only thing you pay for: there is one plan, Team, at one price per seat, with the helpdesk, single sign-on and every other feature in it. A member who has not logged in for a month stops being a seat and costs nothing until they come back; their account and their history stay, so there is nothing to deactivate. A workspace of fifty members or more pays less for every seat, and the page shows the price at your size. The people who raise requests are free, however many of them there are.

You choose whether to pay monthly or yearly when you pick a plan; a year costs the same as ten months, so two months are free, and the choice shows on the Plan and billing page. You also choose the currency, dollars or euros, each with prices of its own; the page shows your price in the one you pick, and it stays the currency of the subscription, so choose the one your company pays in. Seats are counted each night rather than declared, so adding somebody is prorated from that night and taking somebody off shows at the next renewal. A workspace that already has a plan changes it, its card or how often it pays at Stripe; the plans are only offered again once a subscription has ended.

If a payment fails the workspace keeps working for thirty days, with a notice on every page naming the day, and is read-only after that until the payment goes through. A subscription that is cancelled runs to the end of what was paid for; after that a small workspace is simply free again, and a larger one is asked to choose a plan like any other.

Paying, the card, invoices, your VAT number and cancelling are all on Stripe's own pages, reached from Manage billing at Stripe. Alba Ticket never sees a card number. Prices are shown without tax, and Stripe adds what is due where you are.

Deleting a workspace

An administrator can delete the whole workspace from the bottom of the Administration page. The page that follows lists what goes: every project, ticket, comment, board and its history, every attachment (from storage too), every account including your own, all settings and integrations, imported data and the search index. It cannot be undone and no copy is kept.

Export your data first: Administration, Export and import gives you one file with everything in the workspace, attachments included, which can be imported into another Alba Ticket installation or workspace later. Download it before you delete; the export goes with the workspace.

To confirm, type the workspace's address (the part before the first dot) and press the button. The workspace closes at once, so nobody can log in again, and its data is removed shortly after. A subscription is cancelled with Stripe before the workspace goes, and the period already paid for is not refunded. The address becomes free for someone else to use. A self-hosted installation and the demo workspace have no such option.

Inside a workspace

Everything else in this guide applies. The workspace's home page shows its name and how to log in, and its administrators manage it under Administration.