An IT organization employs a team of people to work together to create, manage, and
oversee the service portfolio. The team can consist of strategic, more supportive users, as well
as operational, and critical day-to-day users. Roles assignment is contingent on the
responsibilities and duties of each team member.
System security role assignment
A person with the Admin [admin] role can assign Service Portfolio Management roles to
other users. Assign roles to users based on their individual access needs to create, read,
update, and delete records.
A person with the Portfolio admin [portfolio_admin] role can assign Service Portfolio Management roles to
other users.
Admins or portfolio admins assign roles to system users based on functions, duties, and
responsibilities. Users can perform the necessary functions within the service portfolio,
taxonomies, services, and service offerings they are responsible for, based on assigned
roles.
Service Portfolio Management users
and roles
Common
Service Portfolio Management
team members with typical role assignment include the following users:
- Portfolio owner
- Typically assigned the Portfolio Editor [portfolio_editor] role.
- Strategic role involved in the ownership of a portfolio. This person has overall
authority and accountability for an entire IT service portfolio, typically at the CIO
level. The goal of the portfolio owner is to deliver a portfolio that offers value to
the organization. There is only one portfolio owner.
- Portfolio owners can read and update the entire portfolio that they own. They do not
have access to taxonomies within other portfolios that they do not own.
- Portfolio manager
- Typically assigned the Portfolio Admin [portfolio_admin] role.
- Operational role involved with overall administrative capabilities over a portfolio.
- Portfolio managers can create, read, update, and delete portfolio records of all
types, including portfolios, taxonomy levels and nodes, services, service offerings,
relationships, and performance criteria for the entire business.
- Service owner
- Typically assigned the Portfolio Viewer [portfolio_viewer] and Service Editor
[service_editor] roles.
- Strategic role involved in the ownership of services. Usually at the director-level
within IT, this person is accountable for a given service and its offerings through
the full service life cycle. The service owner typically owns more than one service,
and may even own a branch of services. Typically, service owners are not heavily
involved in day-to-day operations of the service.
- Service owners can read portfolios and existing taxonomy assets, services, and
service offerings. However, they can only update services and service offerings that
they own or delegate.
- Service owners cannot reparent services, or change the service owner. However, they
can add subscriber groups, locations, departments, companies, and users.
- Service owner delegate
- Typically assigned the Portfolio Viewer [portfolio_viewer] and Service Editor
[service_editor] roles.
- Optional role involved in the management of a service. This person is designated as
an editor of a set of services, potentially delegating for multiple service owners.
- Service owner delegates can read portfolios and existing taxonomy assets, services,
and service offerings. However, they can only update services and service offerings
that they delegate.
- Service owner delegates cannot reparent services, or change the service owner.
However, they can add subscriber groups, locations, departments, companies, and users.
For more details regarding roles and assigning roles to users and groups, refer to Installed with Service Portfolio Management for Service Portfolio Management-specific
roles and User administration
for role usage in the platform.
