This repository was archived by the owner on May 19, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Managing Teams and Permissions
archdave45 edited this page Nov 16, 2016
·
9 revisions
An existing member of an Organization can add other users by going to the "Details" section of the organization profile page and selecting "Add Member".
Then, add the member.
As hinted in the section Understanding Public Access Modes and Membership Rights, OCL defines 3 public access properties for each resource:
- View (default) - Any user may view the resource
- Edit – Any user may edit the resource
- None – Only owners may view or edit the resource.
These access properties define the permission levels for NHDD resources and who authorized users are. Resources with Public Access of View can be viewed by all in the system on a read-only basis. Those with a Public Access of Edit are editable by members of the organization that owns the resource.
Example A:
Example B:
- In the examples above, A shows the Source HSTP-IndicatorsVRVAp with a Public Access property of View. As such it lacks the Edit functionality indicated by the
icon.
-
B shows another source HSTP-Indicators with an Edit Public Access property. The provision for making edits is clearly seen by the presence of the
icon next to the source name at the top.
This concludes the Managing Teams and Permissions tutorial.
Overview
- About OCL
- OCL Features
- What is a Terminology Management Service?
- OCL 2017 Roadmap
- OCL Community
- Additional Resources
The Nuts and Bolts
- Getting Started
- Managing Resources
- Searching and Using Dictionaries
- Working with Organizations
- Advanced Topics
- Repository Versioning
- Exporting Repositories
Integration
Other




icon.
