Change one connection without disrupting the team.
People change devices, lose connections and leave projects. Memrain's enrollment controls let the operator act on the affected person while keeping the rest of the shared connector working.
Illustrative example
A teammate has left. Can I remove their connection without reconnecting everyone else?
Revoke that person's redeemed enrollment grant. Memrain removes the tokens issued under it; other members on the connector retain their own connections.
Illustrative scenario, not a live product result.Revoke at the right level.
An unused enrollment code can be revoked before anyone redeems it. For a connected member, revoking the grant deletes the access and refresh tokens minted under that enrollment in one transaction. A separate client-level operation cuts off an entire connector. These controls are available through the operator CLI, with member actions also exposed in the admin Credentials view.
Replace a connection with continuity.
A replacement enrollment preserves the person's source, read set, spend key and daily cap. The existing grant continues working until the replacement code is redeemed, at which point the old grant is revoked. That provides a deliberate recovery path for a new device or a broken refresh chain. Once connected, whoami confirms the source and read set on the new credential.
Handle saved knowledge separately.
Removing a connection retains the source's notes. That lets a team decide what to keep, export, reassign or delete as a separate content decision. Source deletion refuses while content or a live grant still refers to it, making outstanding dependencies visible. Revocation prevents further access through the removed grant; it cannot retract material already copied into a client or another system.
Keep the context. Move the work forward.
Connect your knowledge to the AI you already use. Find your starting point and make the next conversation count.