No. Marking an attribute as multi-valued does not, by itself, cause IdentityIQ to treat that attribute as an entitlement or include its values in the Entitlement Catalog.

In an application schema, the multi-valued setting only indicates that the account attribute can contain more than one value. It describes data structure, not governance meaning.

To include access values in the Entitlement Catalog, the relevant schema attribute must be configured as an entitlement-bearing attribute, or group objects

must be properly configured and aggregated through the application’s group schema where applicable. IdentityIQ then

recognizes those values as governable access rights and can represent them as managed attributes in the Entitlement Catalog. Once cataloged, they can be

reviewed, certified, requested, described, owned, risk-scored, and governed by policy.

For example, an account attribute such as “groups” may be multi-valued, but IdentityIQ must also know that those

values represent access rights. Without entitlement configuration, the aggregation stores attribute values

on the account but does not properly model them as catalog entitlements.

Reference topics: Access Modeling, Entitlement Catalog, managed attributes, application schema attributes,

entitlement attribute configuration, group schema, and account aggregation