Connect Neon to Lutril

Sign in to Neon with an account that is an ADMIN of the organization, then open Account settings and go to API keys.

Create a PERSONAL API key, not an organization one. This is the single most common mistake with Neon: an organization key lists members perfectly and then fails every invitation and every removal, which reads like a broken integration rather than a wrong key type. Neon's own documentation states that organization API keys are not supported for those calls.

Copy the key when it appears. Neon shows it once.

Find your organization ID. It is the org- value in Organization settings.

In Lutril, connect Neon and paste the key and the organization ID.

To time box Neon access, set the access levels on the Neon app in your catalogue to viewer, collaborator, editor and admin. Those are Neon's own role names. Neon also still accepts member as an older name for editor, and Lutril treats the two as the same role so a grant does not re-apply access somebody already has.

A grant only ever raises a role. Anyone who already holds the role they asked for, or a higher one, is left exactly as they were, so a deadline can never take away access that Lutril did not grant.

Neon will not leave an organization without an admin, so a change that would remove the last one is refused with an explanation rather than attempted.

A person whose Neon ACCOUNT is deactivated is refused rather than reported as reinstated. Deactivation belongs to their own Neon account rather than to the membership, and Neon's API cannot undo it, so they have to restore it themselves.

Removing somebody takes them out of the organization and leaves their Neon account alone, so the next grant invites them back.