Sharing
Share links
Section titled “Share links”Share on a collection or an asset makes a link to look and download, at
/s/{token}: approved assets only, and the current version of each.
Request uploads makes a link anyone can send files through, a photographer
or an agency: what they send lands proposed, for review.
Either can end on a date and ask for a password, and revoking one stops it at once. Making one takes write on what it shares.
artbucket share {collection-id} --password dragon --expires 2027-01-31artbucket share {collection-id} --upload --name "Photographer drop"One asset
Section titled “One asset”Nothing leaves the team until someone sends it out. Share on an asset offers four ways out:
- Team: its link in the library, for people who can see it. Nobody else gets in.
- Share link: a page for it, as above, with a password and an end date if you like.
- Signed URL: the file itself, for anyone who has the URL, for an hour to a
year. Add a rendition after the id (
/a/{id}/w_800,f_webp/summer-hero.webp?s=...): the name at the end is only for reading. - Embed: the file for anyone, until turned off, to embed on a site, in a doc or
in an email. It shows two URLs:
/c/{id}, always the current version, the one to embed, and/a/{id}, this version only (delivery). Turning it off stops both.
Sizes and formats, on an approved asset, copies links that follow new
versions (/c/) unless you switch that off; a link signed for anyone names
this version only.
Each takes Editor on the asset, and works only while it is approved and unexpired: archiving it stops all of them at once. Share links and portals sign the files they show a day at a time, so revoking one stops its files within a day.
curl -X POST https://assets.example.com/api/v1/assets/{id}/signed-url \ -H "authorization: Bearer $KEY" -H 'content-type: application/json' \ -d '{"expiresIn": 604800}'People and access
Section titled “People and access”An organization is a team; a project is a library of its own inside
one. What a person may do is their grants: a scope (read, propose,
write, admin) on the organization, a project, a collection or one asset.
Grants add up and reach down: admin on the organization is admin everywhere in
it, write on a collection is write on its assets. Roles are one ladder, with
nothing switched off per grant: an editor edits, approves, deletes and shares;
someone who should only suggest is a contributor. Who sees what
draws it out, with what Who sees it on an asset changes.
Invite people from Settings, People, with Invite people: an email and a role on something. They get a link that works once, for a week.
Projects and organizations
Section titled “Projects and organizations”Settings, Organization, Projects makes, renames and deletes projects; Settings, Organization, General deletes the organization. Both are for its admins, both ask for the name to be typed, and neither can be undone: the project’s assets, collections, brands, keys and links go at once, and its files at the next sweep. An organization keeps at least one project, and a server at least one organization.