You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we definitely want to keep external users to only the collections and/or APOs they are authorized to use.
For internal users, as I understand it (but I could be wrong), the current permissions model in Argo enforces this restriction by allowing them to register items only in the collections/APOs they can access. Since the API includes registration, it will need some way to handle the same permissions.
Not too important for internal projects, but might be a concern if opening to outside users.
The text was updated successfully, but these errors were encountered: