> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grdd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Account and users

> Register a company, check an account and choose the existing Core token workflow.

Use `https://data.grdd.net` for [Connect profile and contact changes](https://docs.grdd.dev/connect-api/company-profile/profile.md). Registration, public duplicate checks and general token operations remain on Core because their matching Connect operations do not exist. A website profile or company-user list is not a registration or duplicate-check replacement.

## Choose your task

| Task | Reference |
| - | - |
| Register a company | [Sign up on Core](https://docs.grdd.dev/connect-api/sign-up.md). Follow its invitation, company-type and caller requirements. |
| Check whether an account exists | [User check on Core](https://docs.grdd.dev/connect-api/user-check.md). The limited response is not a user directory. |
| Get, verify or release an access token | [Authentication and tokens](https://docs.grdd.dev/connect-api/get-token.md). |
| Use the existing vendor-platform client-token workflow | [Client tokens on Core](https://docs.grdd.dev/connect-api/core/partner-impersonation.md). Keep the published prerequisites and authority limits. |
| Change portal settings | [Settings guide](https://docs.grdd.dev/gnet-connect/settings.md). |
| Show a team member on your public website | [Members page](https://docs.grdd.dev/gnet-connect/public-site/members-page.md). This does not create a login user. |

## Keep account authority separate from content

Core issues the credentials used by the documented Connect APIs. Company registration, account checks and client-token issuance remain on their existing Core contracts. A website profile or team-member content record does not replace an account record.

Company user management does not replace the public duplicate check. Use the exact workflow reference for your task. Ask [GRiDD support](mailto:support@grdd.net) for a setup or password-recovery workflow not covered here. Do not copy a private recovery link into an integration.

## Before you use a token

Check the endpoint's caller and company-scope rules. The client token described on the existing [client-token reference](https://docs.grdd.dev/connect-api/core/partner-impersonation.md#use-the-token) has client `MANAGER` authority. It is not a read-only credential. Keep it private and use it only for the documented workflow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.