Connecter Claap à Lutril
Lutril connects to Claap with a workspace API key. It reads your Claap users with their role, their licence and their state, and it time boxes access from both ends: a grant invites somebody or reinstates an account Lutril suspended earlier, and the deadline suspends it again. A grant on somebody who already has a working account raises only their role, and Lutril writes the previous role back when the access ends. Nothing is ever deleted, so every grant can be undone.
Accès demandés
- The key is workspace scoped rather than scope based. It must be created by an Admin or an Owner, because the API and Webhooks settings are only available to those two roles.
- Full access is not required. Lutril reads and manages users and invitations, and never reads recordings, transcripts or deals.
Étapes de configuration
- 1
Sign in to Claap as an Admin or an Owner and open your workspace Settings. The API and Webhooks settings are only visible to those two roles.
Open Claap settings - 2
Open the API and Webhooks tab, then the API tab, and select Create API key.
Using Claap's API - 3
Copy the key as soon as it appears. It starts with cla_ and Claap shows it once, so it cannot be read again afterwards.
- 4
Leave Full access off. It only widens the key to private recordings, which Lutril never reads, and only a workspace Owner can turn it on.
- 5
In Lutril, connect Claap and paste the key. Lutril sends it as the X-Claap-Key header, and the key is encrypted at rest.
- 6
To time box Claap access, set the access levels on the Claap app in your catalogue to member, admin and owner. Those are Claap's own role names, so what somebody requests is exactly what they get.
Claap update user endpoint - 7
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.
- 8
Reinstating an account takes two calls, and Lutril makes both. Claap resets a member's role to Member whenever an account's state changes, so Lutril reactivates the account and then applies the role the grant is for. Without the second step somebody would come back able to sign in but without the access they asked for.
- 9
Guests are listed as guests rather than as members, so a review of who belongs to the workspace does not quietly include people outside your company. A guest cannot be given a time boxed role, because Claap's API cannot set the guest role back again afterwards. Those grants are refused with an explanation rather than made permanently.
Où le créer
Documentation officielle
Connectez-vous à Lutril pour brancher Claap, ou réservez une démo et nous le mettons en place avec vous. Sans slides.