Access should be deliberate, not assumed.

Individual accounts

Each person should use their own sign-in. Trefna can limit an account to one active session, helping to prevent shared credentials. Keep passwords and sign-in links private, and use the account recovery flow if you lose access.

Company and project permissions

Company roles control administration and operational responsibilities. Project access is separate, so people can be limited to the projects and level of access they actually need. Workspace administrators should remove or adjust access promptly when responsibilities change.

Support access

Trefna support does not have standing access to customer projects. A customer must grant temporary access for a stated support request and chooses which project or projects are included.

Support access can be removed by the customer. The product records support requests and access decisions to make this process visible.

Your responsibilities

Use strong, individual credentials, review team membership and project access regularly, and tell us promptly if you believe an account has been compromised. Do not upload information you are not entitled to use.

Security limits

We use technical and organisational measures intended to protect the service, but no system can guarantee absolute security. Customers should retain their own copies of important information and ensure the people they invite are authorised to use the workspace.