Neon
Connect Neon as your access review source using an organization administration key so that the platform can list every member of your Neon organization.
The platform reads the members of your Neon organization through NeonAPIso that you can check who has access.
Prerequisites
Section entitled ‘Prerequisites’- the platform organization administrator access
- The Admin role in the Neon organization (only organization administrators can create an organizational keyAPI)
- The Organization IDwhich the Connect dialog asks next to the key. Neon shows the Settings page, under General information, in the form
org-example-12345678
Collected Fields
Section entitled “Collected Fields”| the platform field | Neon field | Notes |
|---|---|---|
| Name | user.email |
The members endpoint does not expose the display name, so the email address is used |
user.email |
||
| Role | member.role |
admin and member, the two organizational roles of Neon, are displayed as Administrator and Member, and editor, viewer and collaborator as Editor, Viewer and Collaborator. Any other value is displayed as Neon returns it, and a role-free member is listed without a single one. |
| Admin | member.role |
Tagged as administrator when role is admin, corresponding regardless of the case |
| Status | user.deactivated_at |
Listed as active when Neon omits the field and as inactive when Neon returns a deactivation timestamp |
| MFA | user.has_mfa |
Neon reports if the member has enabled multi-factor authentication. Leave unknown when the field is absent |
| Last login | Not supported | |
| External ID | member.user_id |
Stable ID used to track the account through reviews. Returns to member.id, the member ID, when Neon returns no user ID |
| Created at | member.joined_at |
When a member joins the organization |
The platform passes any Neon member returns without an email address.
Step 1: Create an Organization API Key
Step 1: Create an OrganizationAPIKey- In the Neon ConsoleSigned as an organization AdminGo to the organization you want to review and go to Settings > API keys.
- Click Create new and name the key (e.g.
Probo Access Review). Leave it as an organizational key, which covers all the resources of the organization; do not select Project-scoped. - Copy the key and store it securely. Neon displays the token only once, and a lost key needs to be revoked and replaced.
Step 2: Connect in the platform
“Step 2: Connect in the platform”- On the platform, go to Access Reviews > Sources > Add Source.
- Find Neon, click API KeyPress the key and enter. Organization ID, and click Connect.
The platform names the source after your organization and attracts its members to your campaigns.
Troubleshooting
Section “Troubleshooting”- Key rejected. Neon responds to a missing, invalid or revoked key with a 401. Settings > API keys The page is listed there.
- No members appear. Check that Organization ID A project purpose key only reaches its own project and can’t read the organization’s members.
- A collaborator is missing. Someone invited to a single project is a project collaborator, not a member of the organization, so members don’t return them. Collaborators list instead.