Stonebranch permissions establish ownership and ease management of objects. Permissions are applied to objects by matching object names with various naming conventions. These conventions are enforced by the Stonebranch controller, and users will receive errors if they try to name objects incorrectly.
Objects can belong to business services, to individual users, or be shared across all users.
- Any object that belongs to a business service will start with that business service's abbreviation.
- Any object that belongs to a user will begin with that user's username (EID).
- Any object that is shared among everyone will begin with "SHARED_..."
Users cannot see each other's objects. Users with permission to view an object type in a business service can see all objects of that type that belong to that business service.
Permissions are controlled by the Stonebranch stewards. To modify your (or other people's) permissions, contact them at: email@example.com
Naming Convention Standards
- All object names must begin with either:
- four letter Department Code, plus two-digit code (i.e. DEPT01)
- your username (EID)
- The underscore "_" is the only character available as a separator
- Use the correct three-character object type from the table below
- Descriptions can include Stonebranch variables
Note: the * indicates the flexible description that might follow.
|Task||DEPT01_TSK_* or DEPT01_WKF_*|
|Task Instance||DEPT01_TSI_* or DEPT01_WKI_*|