Object access levels
Access levels are default roles that exist for different types of objects. For example, a project has an owner, a participant, a requester, and an approver. A request has an owner and recipient. While the names of the object access roles are fixed, the security permissions granted by them depends on the security policy assigned to the object. In other words, different members of a project might need different access roles. Object access roles are also sometimes called access levels.
HCL® Marketing Operations is a collaborative tool, and users might need varying degrees of access to projects. With Marketing Operations, you can assign different object access roles to project members.
HCL Marketing Operations objects contain the following access levels.
| Access level | Description |
|---|---|
| Owner | All object types have owners, usually the person who created the object. Owners can typically take any action that is associated with an object, such as adding members to the team or editing the properties of the object. |
| Participant | Participants can typically view the object, but not edit it. For projects, when the wizard creates a project, all members added to the project become participants by default. |
| Requester (projects only) | Requesters can typically view the project, but not edit it. If you create a project from a request, the owner of the request becomes the requester of the project. |
| Recipient (requests only) | Recipients can accept or return a request. A requester submits a request to the recipient, who then decides what to do with the request. |
| Approver (approvals only) | Approvers can approve, deny, or suggest changes to an approval assigned to them. |
Sometimes, a project owner needs to change the access levels of a member or members. For example, after you assign people to roles, there are many people with the Participant access level. You can grant some of them owner-level access or deny some of them even participant privileges.