# Lovable + Lutril: setup guide

> Lutril connects to Lovable with a workspace API key and reads who has access to your workspace: every member with their role, whether they are an external collaborator, and whether your identity provider provisioned them. This integration is read only, and deliberately so. Every member route Lovable publishes is a read, so there is no way to invite somebody, remove them or change their role from outside Lovable. A just in time policy can still time box a Lovable request and tell the owner when it runs out, and the owner acts in Lovable.

Source: https://www.lutril.com/integrations/lovable
Category: Developer tools
Auth: api_key
Last verified: 2026-10-08

---

## Setup

1. [object Object]
2. Open Workspace settings, then API keys, and create a key with the workspaces:read scope. Copy it straight away.
3. A Lovable API key is scoped to one workspace. If you govern several, create one key per workspace and connect each as its own Lutril connection.
4. In Lutril, connect Lovable and paste the key. Leave the workspace ID empty: Lutril uses the one workspace the key can see. Set it only if your key sees several, which Lutril refuses to guess between rather than governing the wrong one.
5. [object Object]
6. Lovable's API reports no sign in or last activity date for a member, so Lutril shows no last login column for this app rather than inventing one.

## Access requested

- workspaces:read (list the workspace, its members and its groups)

## References

- [Lovable documentation](https://docs.lovable.dev/features/api-keys)
- [Lovable console](https://lovable.dev)
- [Create an API key](https://docs.lovable.dev/features/api-keys)
- [Lovable API overview](https://docs.lovable.dev/integrations/lovable-api)
- [API reference](https://docs.lovable.dev/api-reference/introduction)
- [Manage workspace members](https://docs.lovable.dev/features/people)
- [Workspace admin settings](https://docs.lovable.dev/features/workspace-admin-settings)