Skip to content

Commit

Permalink
Merge pull request #21 from JoshuaUrrutia/patch-1
Browse files Browse the repository at this point in the history
Update systems-scopes.rst
  • Loading branch information
joestubbs committed Nov 1, 2019
2 parents 7a3cf35 + 411752e commit 793eeeb
Showing 1 changed file with 0 additions and 5 deletions.
5 changes: 0 additions & 5 deletions docs/agave/guides/systems/systems-scopes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -43,11 +43,6 @@ Private systems

All systems are private by default. This means that no one can use a system you register without you or another user with "admin" permissions granting them a role on that system. Most of the time, unless you are configuring a tenant for your organization, all the systems you register will stay private. Do not mistake the term private for isolated. Private simply means not public. Another way to think of private systems is as "invitation only." You are free to share your system as many or as few people as you want and it will still remain a private system.

Readonly systems
----------------

Readonly systems are systems who have granted a GUEST role to the ``world`` group. Once this grant is made, any user will be able to browse the system's entire file system regardless of individual permissions. Be careful when making a system readonly. Usually, the only reason you would do this is because you have configured the system ``rootDir`` to point to a dataset or volume that you want to publish for others to use. Carelessly making systems readonly can expose personal data stored on the system to every other API user. While your intentions may be pure, theirs may not be, so think through the implications of this action before you take it.

Public systems
--------------

Expand Down

0 comments on commit 793eeeb

Please sign in to comment.