Teams
One subscription, a personal key each.
A team plan covers five or more computers at $90 per device per year, billed annually. Nobody shares a key. Each person gets their own by email, and the admin decides how many computers it may run.
For the admin
Invite people from your account page
Open galleryid.ai/desktop/account. Under Seats, click Invite a person, enter their name and email, and choose how many computers their seat allows. They get an email with their key and the download link. The seat shows as Invited until they activate, then lists each computer they’ve activated.
Seat allowances add up against the plan’s device count. A five-device team could be one person with two computers and three people with one each. The page tells you how many are still unallocated.
Managing a seat
Edit · Resend key · Release seat
Edit changes the name or the number of computers. You can’t drop it below what’s already activated; release a computer first. Resend key emails a fresh key and kills the old one. Computers already activated keep working. Release seat kills the key, frees every computer on it at its next check-in, and emails the person. Nothing on their computer is deleted.
For each person
Activate with your own key
Install GalleryID Desktop, open it, and paste the key from your email. Name the computer so your admin can tell it apart. The account key on the plan does not activate anything on a team plan, so if you see “This is a team license”, ask your admin for your personal key. Settings › License shows your seat and how many computers it allows.
Share rosters, code sets, templates and destinations.
Build it once, and every machine on the team has it at its next check-in.
- Rosters. Open the roster and click Share with team. Code sets bound to it go along. Push it again after a change and the button reads Update team copy.
- Code sets. In Rosters › Codes, each set has a Share button.
- Metadata templates. In the metadata editor, Manage… lists your templates with a Share button each.
- FTP destinations and watermarks. In Settings, each destination and each watermark has a Share button. A destination goes out with its password and its watermark; the password is stored encrypted and lands in each machine’s own password store, never on screen.
What arrives
A new roster version, never a rewrite
A shared roster lands on each machine as a new version of that roster. Tags made against the old version keep pointing at it, so yesterday’s captions don’t change when today’s roster arrives. The first time, the roster is created under the same name. Machines pick up changes on their next license check-in, on launch, or right away from Settings › License › Sync now.
Locking
Read-only on every machine but the sharer's
On the account page, Shared with the team lists what’s been shared. Lock an item and it becomes read-only on the receiving machines: a locked roster can’t be saved or refreshed there, a locked code set, template, destination or watermark can’t be edited or deleted. Anyone who needs their own version uses Copy to edit locally (rosters) or Save As… (templates). Remove stops sharing; the local copies stay and just stop updating.
If your team also uses GalleryID Cloud, the purchaser can let a Cloud org manage the seats from its dashboard’s Desktop tab. Billing stays with the purchaser. Cloud is never required.