Editing access levels for a member

IBM® Marketing Operations is a collaborative tool, and people using the software may need varying degrees of access to projects. Marketing Operations accomplishes this requirement, in part, with the ability to assign different object access roles to project members. Object access roles are also sometimes called access levels.

Access levels are default roles that exist for different types of objects. For example, a project has an owner, participant, requester, and 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.

IBM® Marketing Operations objects contain the following access levels.

Object access levels
Access level	Description
Owner	All object types have owners, usually the person who created the object. Owners can typically perform any function associated with an object, such as adding members to the team or editing the properties of the object.
Participant	Can typically view the object, but not edit it. For projects, when a project is created using the wizard, all members added to the project become participants by default.
Requester (projects only)	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)	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)	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 assigning 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.