PRACTICAL FIELD GUIDE
Dashboard login and app-user login are separate
The developer dashboard account manages projects, while app-user authentication identifies people using the application you build. A dashboard session is not a credential for a user's private table rows.
MCPBackend editorial team · · Examples are illustrative
Put it into practice
- Identify whether you are signing into the developer workspace or the generated application.
- Enable the selected project's supported end-user authentication.
- Use the data-plane auth endpoints and returned user token for application requests.
What this looks like
ILLUSTRATIVE EXAMPLE
The developer can see all project records in the dashboard but has never signed up as an end user of the app.
A boundary to keep clear
Do not copy dashboard credentials into frontend requests to make a private screen work.
MCPBackend context
Application email/password authentication is separate from the developer dashboard login and MCP OAuth connection. The current app-user tokens are project-scoped and do not automatically expire. Do not assume built-in refresh, password reset, per-token revocation or social login; check supported behavior before designing those flows.
Take the next step
Inspect the current project contract, try the change with disposable data, and verify the result through the same credentials your app will use. Record the expected response and one denied-access case before release.
Sources and further reading
These references explain the underlying protocols and design principles. For supported MCPBackend operations and exact request shapes, inspect your project’s generated API contract.