Collaborators and several sites

Several people can publish to one site, each from their own Mac. One Mac can also manage several sites.

Invite a collaborator

1. On the Mac that set up the site, open Site Settings ▸ Collaborators.
2. Click Invite a Collaborator…, enter the name of your collaborator if you want, and click Make Invite. Kitset asks for Touch ID.
3. Click Copy Code, and send the setup code to your collaborator.

The setup code holds a secret: a token that can publish to your bucket. Send it through a secure channel, for example a password manager or an end-to-end encrypted message. Kitset shows the code only once.

Your collaborator installs Kitset, chooses File ▸ Join with a Code…, pastes the code and clicks Join. Kitset reads the other settings of the site from the bucket, and the Library of the site opens.

The same steps add a second Mac of your own.

What a collaborator can do

A collaborator can do everything with the videos: publish, edit, replace and delete them, and run bulk uploads and Vimeo syncs. They can change the settings of the site and invite viewers.

Some actions change the Cloudflare account, and they need the Cloudflare Account API Token from the setup. Only a Mac with that token can:

• upgrade the site,
• invite collaborators and revoke their tokens,
• change the list of other players.

To give a Mac the Cloudflare Account API Token, set up the site on that Mac with its own token and the same bucket, instead of a join with a code. Kitset finds the existing site in the bucket and keeps its settings.

Each collaborator needs their own licence, unless your organisation has an Organisation licence. See Licences.

Shared and local settings

The settings of the site are in the bucket, so every Mac and every collaborator sees the same settings: the page folder, the home page, the design, the player, the embeds, the other players and the default audio loudness.

Each Mac keeps its own tokens, its upload settings and the last visibility that it published with.

Tokens

Each Mac and each invite has its own R2 API Token. Site Settings ▸ Collaborators ▸ Show Tokens lists them, after Touch ID. Each token shows its name and its date. “This Mac” marks the token of your Mac.

Revoke… stops a token at once. The Mac or the collaborator with that token can no longer publish. You cannot undo this. Revoke a token when its Mac or its collaborator no longer needs it.

If you manage the R2 API Tokens yourself, make and revoke them in the Cloudflare dashboard.

Several sites

A Mac can have several sites, for example a company site and a personal site. Each site has its own bucket, its own hostnames and its own windows.

• File ▸ Open Site opens the Library of a site.
• File ▸ Set Up a Site… sets up a new site, and File ▸ Join with a Code… joins one.
• Kitset ▸ Settings… ▸ Sites lists the sites of this Mac, each with Open and Site Settings….
• Each window other than the Library has the name of its site in its title, for example “Upload — Example Videos”. The confirm screen of a publish shows the site too.
• A menu command acts on the site of the front window.
• Each site has its own Vimeo token.

Two sites can publish at the same time. Each site runs one job at a time.

When Kitset starts, it opens the Library windows that were open when it quit.

Remove a site from this Mac

Open Site Settings ▸ Cloudflare, and click Remove from This Mac…. Kitset deletes the tokens of the site from the keychain. When this Mac has the Cloudflare Account API Token, Kitset first revokes the R2 API Token of this Mac in Cloudflare. Without it, revoke the token from a Mac that has it.

The site and its videos stay in Cloudflare. Other Macs can still use the site, and you can add it to this Mac again later with a setup code or a new setup.

To delete the site itself, delete its bucket, its Worker and its rules in the Cloudflare dashboard.