Pylon

The platform reads your Pylon organization’s users through PylonAPIso that you can check who has access.

Attention

Use a token created on API Tokens the page from the Pylon settings. Only admin users can create it. Identity Verification Secret is a different credential and will not work because it signs widget users instead of authenticating requests to api.usepylon.com.

Prerequisites

• the platform organization administrator access
• The Admin role in Pylon (only Admin users can create tokensAPI)
• A token created in your Pylon organization that you want to review because a token returns only the users of that organization

Collected Fields

the platform field	Pylon field	Notes
Name	name	Returns to the email address when the user has no name
Email	email	The user’s primary email
Role	role_id	Resolved to the role name through the end point of the Pylon user roles. A user has a role, either a default role (Member or Admin) or a custom one. If the role catalog does not return role_id, the role remains empty
Admin	role_id	Tagged as administrator when the resolved role slug is admin. When a role has no slug, the platform matches the exact name Admin, case-insensitive, so a particular role such as Billing Admin is not tagged
Status	status	The platform lists active as assets and all other values as inactive. Pylon documents away and out_of_office as user states, so both are counted as inactive. A missing state leaves the state unknown
MFA	Not supported
Last login	Not supported
External ID	id	Stable ID used to track your account through reviews
Created at	Not supported

Pylon users are internal members of your Pylon organization’s team, not the contacts and accounts that represent your customers.

___ZBT_I18N_RUNTIME_BLOCK_187__

Pylon values away and out_of_office describe availability, not revoked access. the platform currently displays any state other than active as inactive, so check the user role before deciding whether access should be removed.

Step 1: Create an API Token

1. In Pylon, signed as a Admin, go to Settings > API Tokens.
2. Create a token and name it (e.g. Probo Access Review). The actions the token performs appear under the token name.
3. Copy the token and store it securely, for example in a password manager.

Step 2: Connect in the platform

1. On the platform, go to Access Reviews > Sources > Add Source.
2. Find Pylon, click API KeyHold it in your hand and click Connect.

The user endpoint does not return an organization name, so the platform lists the source under the fixed name Pylon and attracts the organization’s users into your campaigns.

Troubleshooting

• Token rejected. Confirm that the token comes from the API Tokens If you no longer have the token value, create a new token instead of trying to recover the old one.
• Token creation is unavailable. Only administrator users can create tokens API. Ask an administrator in your Pylon organization to create the token or give you the administrator role in Users page.
• No users appear. Confirm that it was created in the Pylon organization you want to review and that the members you expect are Pylon users, rather than customer contacts.
• A user is listed inactive, who still has access. Pylon uses status for availability, including away and out_of_office, and the platform lists any status other than active as inactive.