The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Self Service Catalog allows you to create a hierarchical structure of parent and child Organizational Units (OU). Each OU can have a parent OU and one or more child, or sub, OUs.
OU structure has the following effects:
Because you are adding sub-OUs to a parent, a helpful way to order your work is to:
Step 3 Add the sub-OUs to the parent OU.
Step 1 Log into the Service Portal.
Step 2 On the Organization Designer Home page, click the Create Organizational Unit link in the Common Tasks pane.
Additionally, you can create an organization unit by clicking Add on the Org Units page.
Step 3 ( Required ) In the General pane, enter a name for the new OU. For this example, IT TES .
Step 4 ( Required ) Select a status for the OU, Active or Inactive .
Step 5 Select the Billable option if the new OU will have billable business units.
Step 6 ( Required ) Select one of the following organizational unit types:
Access to the capabilities provided by Portal Designer is controlled via standard Role Based Access Control (RBAC). Design personnel can be granted access to all or selected portions of the Portal Designer functionality. Access to the functionality of the portal front-end, including the ability to customize the portal by adding portlets or changing the look-and-feel of the portal pages, may also be controlled via RBAC. Details on the portal-related capabilities and how to assign these to project personnel are given in the Cisco Service Portal Configuration Guide and in the online help for Organization Designer regarding roles.
Similarly, end users’ ability to access the portal front-end can be controlled via RBAC. Only users with a role that includes the “Access Service Portal” capability will be able to see the “Service Portal” module menu and navigate to the portal pages and portlets.
As described above, Service Portal RBAC allows administrators to control which people, organizational units, or groups can access certain modules, and capabilities they can perform within each module. Further, those permissions can be allowed to operate on all entities (objects) of a particular type, or restricted to a set of named entities. A role, therefore, combines access to a module with one or more capabilities, and in some cases, one or moOrganizations, Roles, and Users Preparationre object-level permissions.
The Service Portal provides several system-defined roles, which group capabilities into sets of responsibilities that might typically be assigned to participants in a Service Portal implementation. Site administrators can supplement these roles with custom roles, to better suit the division of responsibilities on a particular implementation team.
All members of the organizational unit inherit the roles assigned to the organizational unit. In addition, sub organizational units inherit roles from their parent organizational unit.
Step 1 On the Organization Designer Home page, click the Create Role link in the Common Tasks pane.
Additionally, you can create an organization unit by clicking Add on the Roles page.
Step 2 ( Required ) In the General pane, enter a name for the new role. For this example, TES Common Portal Reader .
Step 3 If this role has a parent, enter (or browse) the Parent role.
Step 4 Select a status for the role, Active or Inactive .
People are all the individuals who either receive services via My Services or provide services via Service Manager, as well as all the administrators, managers, and users of all other application modules.
You must set up all individuals who are system users, whether they are within or external to your organization. The following two statements are important to remember:
Step 1 On the Organization Designer Home page, click the Create Person link in the Common Tasks pane.
Additionally, you can create an organization unit by clicking Add on the People page.
Step 2 ( Required ) In the General pane, enter the First Name and Last Name of the person.
Step 3 ( Required ) From the Status list, select a status for the person, Active or Inactive .
Step 4 ( Required ) From the Language list, select the language to display on the user interface for the person. If not provided, English is used.
Step 5 ( Required ) From the Time Zone list, select the time zone associated with the person's primary address. If not provided, the default server time zone is used.
Step 6 ( Required ) In the Login field, enter a unique login identifier.
Step 7 ( Required )In the Password field, enter a password used to log on to the system. If using Organization Designer, retype the password to confirm. Any character in the character set supported by the application can be used in the password.
Step 8 (Required) Click Update / Add.
As described above, Service Portal RBAC allows administrators to control which people, organizational units, or groups can access certain modules, and capabilities they can perform within each module.
Step 1 On the Organization Designer Home page, click the Create Person link in the Common Tasks pane.
Additionally, you can create an organization unit by clicking Add on the People page.
Step 2 In the General pane, select the role you want to assign to this person.