Access

The TellusR solution has two distinct access levels. This section outlines access and authentication.

Access

TellusR has two predefined users with different access levels:

Admin User (admin) Has access to both the dashboard and admin operations in the API, such as managing semantic indexing. Required for performing administrative tasks. See how to set the password using admin_password.

General User (tellusr) Has access to general API operations, such as managing projects, uploading documents, and querying data. Cannot perform admin-level API actions and does not have access to the dashboard. See how to set the password using password.

We highly recommend changing the default passwords just after installing the TellusR solution using the password and admin_password commands. The default password for both users is TellusRSwings.

Keycloak Identity & Single Sign-On (SSO)

For enterprise identity management, TellusR integrates with Keycloak. You can either use the Keycloak instance that can be self-hosted alongside your TellusR deployment, or connect TellusR to your organization’s existing third-party Keycloak setup.

Through this infrastructure, TellusR supports Single Sign-On (SSO) authentication via external OpenID Connect (OIDC) providers. This allows your users to log in using identity platforms like Microsoft (Entra ID), Google Workspace and others.

Current Implementation Status

Currently, SSO is implemented for our end-user UI. The admin dashboard still relies on the built-in Admin User. Contact us for more information about how to configure SSO in your organization.

Roadmap: Advanced Organizational Access

Currently, granular data access is securely handled at your application layer using configurable search filters. Moving forward, we are expanding our Keycloak integration to introduce native, enterprise-grade access controls directly within TellusR.

This work-in-progress will introduce organization‑level and user‑level access to various resources in TellusR, ensuring that each registered organization has total control over who can access and work with its data.

Planned areas:

  • Project Access: Projects will be securely owned by an organization and restricted to its verified members.
  • Document Access: Granular read, write, and share permissions for specific groups and members within an organization.
  • Assistant Access: Fine-grained control over assistant visibility, usage limits, and administrative rights.