Local and Team libraries.
Where Vault keeps your assets, how to change the Local folder, join a team, and move an asset from Local to a team.
Local Library
The Local Library is a folder on your computer. Each saved asset is its own
subfolder holding the package, the thumbnail and a small recipe.json describing
it. There is no upload, no sync and no account.
By default the folder is inside Altar’s data folder. To use your own (a project drive, a synced folder), open Settings → Vault → Change folder, or Change Local folder in the libraries menu in Browse. Altar reads whatever is in the folder you choose and does not move your existing assets for you.
A few useful facts:
- Browse reads the folder when you open it and when you press Refresh (the circular arrow in the Browse header). Copy an asset folder in by hand, then Refresh.
- A bare
.aepor.ffxfile dropped into the folder also shows up, named after the file. It has no thumbnail or recorded requirements until you save it properly. - If the folder cannot be read, Browse says so and points you at the folder menu.
- Deleting an asset in Browse removes its folder from disk. It does not go to the Trash. Altar asks you to confirm first.
Team Libraries
A Team Library is private storage shared by one team. Members browse it next to Local, add from it, and save to it.
Join a team
Open Settings → Teams, paste the invite code and join. Codes are single use and expire, and joining needs a signed-in Altar account. The team then appears in the libraries menu on its own. You do not need to restart anything.
Roles
- Admin - everything below, and can delete any asset in the library.
- Member - browse, add, save, and delete assets they saved themselves.
The panel also reserves a read-only role. A person with it can browse and add, but the Save page refuses with a permission message. The server decides what is allowed. If a button is missing or a save is refused, that is the role at work.
Limits
A team asset can be up to 250 MB in total, and the team has a storage allowance (10 GB by default). See Storage and packaging limits.
Browse several libraries at once
The libraries menu in the Browse header (it reads All libraries when everything is on) has a tick for Local and one for each team, plus Select all and None. A team you have just joined arrives ticked. Your choices are remembered. When more than one library is showing, every card shows its library’s name.
If one library fails to load, the others still show, with a message and a Retry button.
Screenshot pending: the libraries popover open in the Browse header, Local and one team ticked.
Move an asset from Local to a team
Select a Local asset, open the arrow beside Import, and choose Move to followed by the team name, for example Move to Studio (shown only for teams you can save to).
- For each of the asset’s tags, Altar looks for the same tag in the team’s list. If a close match exists it asks whether to use it, and if none does it asks whether to create the tag or leave it off the team copy.
- The asset uploads with a progress readout.
- Only after the upload succeeds is the Local copy removed.
A failed upload leaves the Local copy untouched. If the upload works but the Local copy cannot be removed, Altar says so and both copies stay. Favourites, Collection membership and Recently used history move to the team copy.
The reverse, team to Local, is not available. Add it to a project from the team library and save from there if you need a Local copy.