- designating a person to perform certain data operations
- saving your work with a bookmark or creating / working on a personal branch
- being aware of who is using your data container / data before performing operations
locking a container to prevent others from performing any operations on it
How many owners should a container ideally be shared between?
There is no technical limit built into the software, but it is best if a team of 5-10 users shares a single data container. In most cases, having fewer owners minimizes overhead and conflicting usage. One owner per container provides maximum productivity and minimal overhead, so this feature should only be used if your infrastructure or processes require that multiple users share a container. Additionally, Jet Stream Only users currently cannot see other users with whom they share the container.
How should users handle potentially disruptive operations?
If one user performs an operation on a data container, it will affect the other owners of that container. Additionally, each user has permission to perform the same operations on the data container; currently there are no fine-granularity permissions that limit the operations a user can perform. All operations are potentially disruptive, but the level of disruption varies by operation. If any of the following operations are performed at the same time, the second operation will fail due to a conflict when processing the job.
If User A performs a destructive operation while User B is "using" the data container, the operation will destroy User B’s current state. Currently, the interface does not provide insight into whether the data container is in use by another user.
All owners can delete any bookmarks or branches in the container, regardless of who created them.