---
title: Configuring Service Attributes
slug: citsmart-8-en/configuring-service-attributes
description: Learn how to configure service attributes in Portfolio and Catalog Management for Business/IT Service and Support/Technical Service portfolios. Discover the procedure to access and configure attributes and gain insight into various attributes you can conf
docTags:
createdAt: 2022-01-19T21:40:22.000Z
---
The service attributes are configuration features within the portfolio.
The guidance described in this knowledge can be followed to **configure the
attributes of both portfolio types, Business/IT Service and Support/Technical
Service**, within Portfolio and Catalog Management.
## Before getting started
Service attributes are preceded by subscriptions to other features, such as:
- [x] The
Services portfolio, a group, configuration items, a calendar, a contract, and a
cycle.
## Procedure
1. Access the main menu `Processes > Portfolio and Catalog Management > Portfolio`;
2. Access the Service Portfolio you want and click on "**Advance**";
3. Click on "**Advance**" in the service to access it;
4. On the left side, the different attributes that can be configured are presented.
| **Name** | **Type** | **Objective** |
| -------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Details | Attribute | It allows to change/update the service data |
| Service Level Requirements | Attribute | It allows registering the service level requirements |
| Financial Attributes | Attribute | It allows registering the service financial attributes |
| Business Cases | Attribute | It allows registering the business case of the service. This business case is a summary of all service information |
| Service Map | Attribute | It allows setting the design of a service map related to the enabling services and configuration items. In this design, it's defined which enabling service will be used to perform the main service |
| Business Processes | Attribute | It allows liking the business processes that are not supported by the service |
| Support Services | Attribute | It allows liking the support/technical services. Those services support the main service |
| Business Owner | Attribute | It allows liking the business owner to the service, which can be employees or groups |
| Business User | Attribute | It allows liking business users to the service |
| Requests | Attribute | It allows registering the service activities requests |
| Applications | Attribute | It allows liking the applications that will be used to run the service |
| Data Schema | Attribute | It allows registering the data schema of the service |
| Incidents | Attribute | It allows registering the service incident activities |
| Procedures | Attribute | It allows registering the procedures for the service, which will be used by the continuity management to trigger and control the service restoration activities |
| Contracts | Attribute | It allows liking the contract that provides the service |
| IT Owners | Attribute | It allows liking the IT service owners to the service, which can be users or groups |
| Knowledge Base | Attribute | It allows liking the knowledge to the service. The knowledge is an information of the service provider to deliver the service |
| Skill/Resource | Attribute | It allows liking the skills/resources to the service |
| Capacity/Performance | Attribute | It allows liking indicators of capacity/performance to the service |
| Attribute of Demand | Attribute | It allows liking demand attributes to the service |
| Service Evaluations | Attribute | It allows managing the service evaluations that were registered via Smart Portal |
| Service Audit | Attribute | It allows verifying the history of service to audit it |
### Service Level Requirements
:::hint{type="info"}
**🖊 ****Note****: **Information available to maintain Service Level Requirements: Creation date, Service start date,
Service owner, Service utility, (Specification, Context, Essential Functionalities), Service
guarantee (Security, Availability, Capacity, Business Continuity, Performance, Planned Interruptions),
Service Support (Incident Management, Problem Management, Change Management), Conformity (Internal,
External) and Attached documents.
:::