epismo 1.15.0 → 1.16.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -1
- package/npm/vendor/darwin-amd64/epismo +0 -0
- package/npm/vendor/darwin-arm64/epismo +0 -0
- package/npm/vendor/linux-amd64/epismo +0 -0
- package/npm/vendor/linux-arm64/epismo +0 -0
- package/npm/vendor/windows-amd64/epismo.exe +0 -0
- package/npm/vendor/windows-arm64/epismo.exe +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -67,9 +67,10 @@ Use `visibility` and explicit editors instead of a raw ACL:
|
|
|
67
67
|
```sh
|
|
68
68
|
epismo playbook access get PLAYBOOK_ID
|
|
69
69
|
epismo playbook access set PLAYBOOK_ID --visibility public --editors USER_ID,TEAM_ID
|
|
70
|
+
epismo playbook owner PLAYBOOK_ID --owner-id WORKSPACE_OR_USER_ID
|
|
70
71
|
```
|
|
71
72
|
|
|
72
|
-
`public` permits published reads only. Editors can read and edit Playbook content; the owner
|
|
73
|
+
`public` permits published reads only. Editors can read and edit Playbook content; the owner, and every member of a Workspace-owned Playbook, are implicit and are not included in `--editors`. Workspace members can read and edit Playbooks owned by a Workspace they belong to. Owner managers, including Workspace Owners and Admins for a Workspace-owned Playbook, manage access, public visibility, and archive Playbooks or historical Versions. Any member may create a Playbook owned by a Workspace they belong to, or move a personally owned private Playbook into it with `playbook owner`.
|
|
73
74
|
|
|
74
75
|
## Cases and handoffs
|
|
75
76
|
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|