Import details of app users from a .csv file or Excel spreadsheet.
You can import user information for a particular app using an Excel spreadsheet or .csv file. This is useful for apps that do not benefit from a direct integration and for which usage data is not available from your identity provider (IdP).
Importing app user data into Trelica helps you to build a complete picture of app usage within your organization. By recording who has access to particular apps you can:
- Monitor user engagement and optimize license allocations.
- Ensure new starters have access to the apps they need.
- Manage removing access to apps when people leave your organization.
Importing user data for apps without integrations
If app user data is not available from an integration, we recommend updating user data via an import at least once a month.
You can use an import both to record new app users and to update details for existing app users. When importing app user data regularly, it's important to use a consistent data format and apply the same field mappings each time. Many apps allow you to export app user details to an Excel spreadsheet or .csv file, which you can then import to Trelica directly.
Importing app users to Trelica manually does not create or update users in the app itself. To be able to create or update app users from Trelica, set up a direct integration or manage the app via an IdP integrated with Trelica. For more information, see Grant Trelica access to applications.
To import user information for a particular app:
-
Open the Apps inventory and select the app for which you want to import user data.
-
Select the Users tab. Any app users that have previously been recorded in Trelica are listed. This may include users discovered by an existing IdP integration (such as Okta, Google Workspace or Microsoft Entra ID) and users that have been added manually.
-
Expand the context menu and select Import. The app user import wizard is displayed.
-
Select the file containing the user data for the app. Any app users that have previously been recorded in Trelica via an import should be included in the file. Any users created from a previous import that are not included in the file will be deleted.
-
Date and time exported records when the user data was exported from the app. This information is used to determine the accuracy of the app user data. Change the date and time as required and then click Next.
-
The Mapping step is displayed. Trelica attempts to map the fields in the file to fields in Trelica. To add or change mappings, click the drop-down boxes and select from the lists. Data from any fields that are not mapped is not imported.
-
Email - The email address of the app user. This must be provided for each user in the file.
If you are recording a new app user and the email address matches an existing person record, the app user details are associated with that person. If the email address does not match an existing person, a new person is added to the People directory.
If you are updating an existing app user and the data does not include a user ID (see below), Trelica uses the email address to match details to existing app users. - Status - Indicates whether the user account in the app is active, suspended, deactivated or archived. If a status is not provided, new users are set to active by default. To update the status of an existing user, a new value must be provided.
- Role - The user's permission level in the app. This is useful for recording which users have administrator access or other elevated permissions.
- License - The type of license assigned to the user. Recording which tier or license type has been allocated to each app user is useful for understanding usage and calculating potential savings. Where applicable, ensure the text matches the license plan name displayed on the App Licenses tab.
- Last login - The date of the user's last login to the app. This information is useful for determining user engagement so that you can optimize app licenses.
- Created date - The date the user account was created in the app.
- Full name - If app users' names are split into first name and last name in the file, select Full name is split into columns for first and last name from the options below the mapping table.
- User ID - A unique identifier, such as a user name. This may be provided in addition to the user's email address. When updating existing app user details, user ID is used in preference to email address to match the imported data to existing records.
-
Email - The email address of the app user. This must be provided for each user in the file.
-
Once you have finished mapping the fields, click Import. The progress of the import and the changes that are made as a result of the import are displayed.
-
Once the import is complete, click Review. The App Users list is displayed, filtered to active and suspended users. To view all app users, clear the Status filter.
Click an app user to view their details, including a link to their Person profile.
To update an individual app user's details, expand the context menu and select Edit in Trelica. To make changes to multiple app users, import a new file.
Importing usage data for apps with integrations
As a general rule, we do not recommend importing app usage data manually if app user data is already available from an integration. This is because the imported data would be overwritten the next time the integration runs.
If the app user data supplied by an integration is incomplete, you can import the missing data manually. When importing missing data, please note the following:
- The import file must include a unique identifier for each app user, such as the user's email address.
- Only the column containing the unique identifier and the column(s) containing the missing data should be mapped to fields in Trelica. If the file contains other data points that are already provided by the integration, either remove them from the file or unmap those columns before completing the import.
- If you are importing missing data regularly, ensure you use the same file format and mappings each time.
If the data supplied by the integration is incorrect, it should be fixed in the source system. If you're experiencing problems with an integration, please contact Trelica Support & Customer Success team.
Comments
0 comments
Please sign in to leave a comment.