How does user provisioning work in Pylon?

Pylon can create two different kinds of user records automatically, and they are handled differently.

When Pylon sees someone through a connected integration such as Slack, it can create or link an Integration User. Integration Users help Pylon attribute messages and assignments, but they do not count as paid seats and cannot log in to the Pylon web app.

Auto-provisioning for login access

Automatic creation of a full Pylon user is separate from integration-user creation. Full users are typically created when someone logs in for the first time and your workspace allows domain-based access or another login-based provisioning flow.

If you want stricter control, you can require invitations before anyone gets web-app access. In Settings > Users > Access Settings, enable Invite Only to prevent automatic creation of login-enabled users.

What this means in practice

• Slack activity can create an Integration User record even if the person never logs in.

• Integration Users appear in your workspace for attribution and assignment, but they do not have web access.

• Login-enabled users are controlled separately by your workspace access settings.