While the permissions object is intended to hold permissions presence in the permissions object as a key implies view/read access for now until we implement checks and update middleware chains for more complex permissions. Keys are intended to be user, team, or org IDs with a mapping to permissions.

permissions
object
required

Permissions mapping where keys are user, team, or org IDs and values are permissions. Presence implies view/read access.

mode
enum<string>
required

The mode of sharing.

Available options:
restricted,
team,
public