> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/getting-started/credentials.md).

# Choose Credentials

Choose Platform, Classic, or Scribe credentials, confirm the tenant and host, and verify access before starting a workflow or installing a client.

For a new Platform integration, start with your assigned workspace, regional API base, and a credential accepted by the operation you need. Keep the API family and base URL alongside the tenant identifier in your integration configuration.

## Choose the Access Boundary

| Your task                                                            | Tenant and caller                                           | Credential and owning guide                                                                                                                     |
| -------------------------------------------------------------------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Read or configure Platform workspace resources from a trusted server | One workspace; permissions of the key or token              | [Platform workspace keys](/developer-guide/platform-api/platform-api/authentication.md) on routes that accept them                              |
| Run a scoped backend integration                                     | Workspace and scopes granted to the client                  | [OAuth2 machine-to-machine](/developer-guide/platform-api/platform-api/oauth2.md)                                                               |
| Use managed channels with your own agent or backend                  | Provisioned setups and granted channel operations           | [Standalone Channel Manager OAuth](/developer-guide/platform-api/conversations/channel-manager.md#authenticate) on its separately assigned host |
| Sign in interactively to a CLI or desktop application                | Signed-in identity and selected workspace                   | [Device authorization](/developer-guide/platform-api/platform-api/authentication.md#device-code-flow-cli-and-desktop-apps)                      |
| Create or review clinical documentation                              | Provider principal, owning provider, and matching workspace | [Scribe provider access](/developer-guide/platform-api/scribe.md#authentication), with the scope required by the operation                      |
| Maintain a Classic integration                                       | Organization and authenticated user                         | [Classic key-to-token exchange](/developer-guide/getting-started/authentication.md), then a Classic SDK or HTTP client                          |
| Query Classic data through the standalone Data-MCP service           | Classic organization and user                               | [Data-MCP](/developer-guide/platform-api/data-world-model/data-mcp.md)                                                                          |

API keys, identity tokens, provider tokens, and channel-management credentials have different access boundaries. Similar route names do not make their hosts or authorization rules interchangeable. For browser applications, follow [Serve an Agent From a Web App](/developer-guide/platform-api/conversations/serve-agent-from-web-app.md); keep long-lived workspace credentials on the trusted server.

## Verify Platform Access

1. Obtain your workspace ID, assigned [regional endpoint](/developer-guide/getting-started/regions-and-endpoints.md), and the required read permission from the implementation owner.
2. Configure the [Platform SDK](/developer-guide/platform-api/platform-sdk/configuration.md), or use the workspace-key HTTP example in [Authentication & API Keys](/developer-guide/platform-api/platform-api/authentication.md#api-key-usage).
3. Run the read-only [SDK quickstart](/developer-guide/platform-api/platform-sdk/quickstart.md). Confirm the returned workspace matches the intended test deployment.
4. Select an explicitly configured test service before running [First Verified Conversation](/developer-guide/guides/first-verified-conversation.md).

A successful read verifies access to that resource. It does not verify channel provisioning, tool permissions, provider enrollment, or external delivery.

## Diagnose Access Failures

Check the API family, host, tenant identifier, credential expiry, and required scope or permission before repeating a request. Use the route's documented error response to distinguish authentication failure from insufficient access or an unavailable resource. Preserve the correlation identifier when one is supplied, and use [Troubleshooting](/developer-guide/guides/troubleshooting.md) to identify the next diagnostic.

## Sessions Mean Different Things

| Session                 | Purpose                                         | Continue here                                                                           |
| ----------------------- | ----------------------------------------------- | --------------------------------------------------------------------------------------- |
| Identity session        | Login, token validity, and account access       | [Platform authentication](/developer-guide/platform-api/platform-api/authentication.md) |
| Persistent text session | Connection and interaction protocol             | [Platform Sessions](/developer-guide/platform-api/platform-api/sessions.md)             |
| Scribe session          | Provider-owned clinical encounter and artifacts | [Scribe Sessions](/developer-guide/platform-api/scribe/sessions.md)                     |

Ending a conversation, disconnecting a socket, finalizing a clinical note, and revoking a login are different operations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.concurrence.com/developer-guide/getting-started/credentials.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.