Account Attributes

The Salesforce connector returns several attributes falling into two categories. The first are general attributes: name, city, state, and so on. Additionally, there are entitlement attributes that specifies user level access granted to Salesforce:

The account user's display name, typically in an email type format

For example, denise.hunt@demoexample.com

The internal Salesforce ID number for the account

The format is as follows:

005A00000014ySyIXX

This is an Identity Attribute which must not be changed.

The user's full name

The user's first name

The user's last name

The user's assigned alias

The user's city

Display Names for the user's online communities

The user's call center

The user's company name

The user's country

The user's department

The user's Email address

The user's division

The user's employee number

The user's telephone extension

Name of the street

The user's fax number

A Federation ID is an identifier that is unique within a Salesforce Organization

Indicates if the user account is active in Salesforce

When set to false, the user account is disabled

Encoding that should be used during email communications

ID of the profile assigned to a user

Profiles contain settings and permissions, which control what users can do. The available profiles depend on which user license is selected.

Name of the profile assigned to a user

Profiles contain settings and permissions, which control what users can do. The available profiles depend on which user license is selected.

The role assigned to a user

Public groups are the entitlements for a user

Queues assigned to the user.

Aggregates the Queue Names associated with an account. It also supports provisioning operation for Queue Names associated with the account.

This attribute can be deleted if not required.

Maps to the Marketing user flag

Maps to the Offline user flag

The user's phone number

Enable to receive the salesforce.com administrator newsletter

Type of the user

Enabled if the user is a Portal User

This field is read-only.

Enabled if the user is a Partner User

This field is read-only.

Maps to Sales Anywhere User

Enable to receive the salesforce.com newsletter

Permission set assigned to a user

A permission set contains settings and permissions which control a user's action. The available permission depends on which user license is selected. Users can have multiple permission sets.

Note
For more information on aggregating the PermissionSet attribute as group object, refer to Upgrade Considerations.

PermissionSetGroup represents a group of permission sets and the permissions within them. Use the PermissionSetGroup attribute to organize permissions based on job functions or tasks. Users can have multiple permission set groups.

Note
For more information on aggregating the PermissionSetGroup attribute as group object, refer to Upgrade Considerations

Permission set license assigned to a user

Managed package assigned to a user

The user’s license

The user's state

The user's title

The user's timezone, it uses a display name defined by Salesforce. Only a few timezones are defined in the policy drop down and this will need to be customized for each deployment.

Defaults to America/Los_Angeles

The user's locale

Defaults to UTF-8

The email encoding key

There are several selections to choose from in from the web interface. The encoding keys are customizable.

Defaults to UTF-8

The language locale key

There are several selections to choose from in from the web interface. The locale keys are customizable.

Defaults to en_US

The user’s manager' ID

 

Note
The ProfileId and UserRoleId fields are required in the schema to aggregate the ProfileName and userRoleName respectively. If the ProfileId or UserRoleId is removed then profile name and user role name will not be fetched.

Additional Account Attributes for the Salesforce Connector

  • (For attributes present on user object only) The Salesforce Connector enables you to aggregate and update custom attributes present on user objects. The custom attributes added in the Salesforce user schema must have __c appended to the attribute names created in Salesforce.

    For example, if you added EMP_DEPARTMENT in the user entity on the Salesforce system, you should also add EMP_DEPARTMENT__c in the Salesforce user schema.

    Note
    Custom attributes can also be updated.

  • Support for custom attributes not present in Salesforce system but are required internally in SailPoint, such as for a configured correlation rule can be acknowledged if the attribute is prepended with _#.
    For example:

    _#Emp_company_history