Developers
Authentication
Claura currently authenticates product users and authorizes every request against their active workspace and membership.
User sessions
Application requests use the signed-in user session. The active workspace is sent as workspace context and is validated on the server.
Workspace authorization
Membership is the source of truth. Relationship access to a client workspace is kept distinct from direct membership and ownership.
API keys
Self-service public API keys are not currently documented. Never reuse browser session credentials or copy internal tokens into an external integration.
CLAURA NOTE
Financial context should stay connected.
Claura keeps the document, conversation, and decision together—so the next person never has to reconstruct the story.
found in Claura documentation · Financial memory