Skip to main content

Authentication and access

Module authentication controls who can reach the applications you deploy. Intellectible handles sign-in at the application's address, before protected requests reach your server.

The settings belong to the module, not an individual deployment. They apply across its deployments and supported custom domains, so review the effect on staging as well as production when changing them.

Project collaborators and application users​

These are different kinds of access:

  • Project collaborators build and manage the project, subject to their project roles.
  • Application users sign in to the deployed application and receive the app roles you assign.

Inviting somebody to use an application is not the same as giving them access to edit its code or manage its project.

Configure sign-in​

  1. Open Authentication → Settings in the module editor.
  2. Turn on Require sign-in.
  3. Choose the sign-in methods: Email and password, Email link, or both.
  4. Choose whether accounts are invite-only or users can register themselves.
  5. Configure the access policy and review any public-path exceptions.
  6. Save and check the publication result, then test the deployed application while signed out and with an intended user's account.

Authentication settings publish without rebuilding the application. If publication reports an error, resolve it and verify the deployed URL before assuming the change is enforced.

Public access

When Require sign-in is off, deployments are public at the platform gateway. Do not disable it to troubleshoot an application containing private data. Use the relevant logs and test accounts instead.

Users, roles, and access policies​

Use Authentication → Users to manage application accounts, invitations, and role assignments. Use Roles to define reusable roles for the module.

The access policy determines which signed-in users can reach the application. You can allow all registered users or restrict access using conditions such as roles and email domains. Registration and access are separate decisions: allowing somebody to create an account does not necessarily allow them through the access policy.

A role name does not implement permissions on its own. Use the gateway policy for entry restrictions and server-side application checks for actions such as editing an invoice or viewing another user's records. Hiding a button is not a security check.

Public paths​

Public paths bypass deployment sign-in for matching routes. They can be useful for a deliberately public endpoint, but the exemption applies to every HTTP method on that path.

Use narrow rules and the Try a path checker before saving. A “starts with /” rule makes the whole application public. Query strings do not narrow the exemption. If a webhook endpoint is public, the application must still verify the sender appropriately.

User identity and appearance​

The User identity option can pass verified identity information to your backend. Browser code can use the gateway's /__intellectible/me endpoint on the application host to check identity. Treat unauthenticated and public-path requests separately; a request arriving through the platform is not automatically signed in.

The Sign-in page controls let you customise the appearance. Keep access rules in the authentication settings and application code, rather than relying on the design of the sign-in screen.

Development previews have an additional developer-access gate. See Development previews if you are testing authentication before deployment.