Idea : if read permissions are filtered, users will want to make some artifacts public

Issue #2222 discussed the idea of making read permissions controlled more granular (see below). An implication might be that a user would like a simple way to make a given artifact publicly viewable (readable to all other users). Without some additional work to that proposed in #2222, the user would have to manually select every other user of the system to grant read access. Thus, it might be appropriate to add the ability to do so with a single check box (or other ui element) in the user interface.

The implications would be as follows:

• there would be a need for a new system role that is granted to every user, that is not easily deleted, and that would initially be have no permissions assigned. As users select to make their artifacts public, the read permission for each artifact would be added to the TBD role and thereby make it possible for all users to see the artifact in lists such as the concept set or cohort lists.

flowchart LR
    A[design artifact] -->|edit| B(save)
    B --> |edit| C{write access}
    C -->|group| E[all users in a  group]
    C -->|user| F[single user]
    B --> |edit| D{read access}
    D -->|public| G[global read]
    D -->|group| H[all users in a  group]
    D -->|user| I[single user]

NOTE: In Atlas, this could be implemented by change the modal form presented after clicking the the lock icon present in the concept set expression view to allow the user to edit both read and write access:

Start by reading issue #2222 and the Atlas concept set expression view, especially the lock-icon modal mentioned here. Done would require an agreed design for making an artifact publicly readable, including how the all-users role and read access should behave.