CentralizeMe

Project Basics

Reviewed against the implementation —
In this category

CentralizeMe is organized around the project. A project gives one client, product, or service a clear place for its credentials, health information, and access decisions.

Before you begin#

Have a CentralizeMe account, a project you are responsible for, and one credential whose owner and purpose you can identify. For a first pass, use a non-production credential or a credential you are prepared to manage in this project.

The first-project goal is simple: establish the project boundary, add the credential with enough context to find it later, and check that the resulting access and health information are visible where you expect them.

Create your first project#

  1. Sign in to CentralizeMe and create a project for one client, product, or service. Use a name that will still be clear when you have several projects.
  2. Add the credential to that project. Record useful metadata such as what the credential is for, who owns it, and where it is used. Keep the secret value in the credential field rather than in project descriptions, notes, or links.
  3. Review the project’s access scope before inviting anyone. Project-scoped access is the boundary to use when deciding who should see or manage the credential.
  4. Check the project’s health or status view. Health information is part of the project view, so it should remain easy to find alongside the project details and its operational areas.

Verify the setup#

Use this checkpoint before adding more projects or sharing access:

  • The project name identifies the client, product, or service without relying on a private note.
  • The credential appears in that project with enough metadata to distinguish it from another credential.
  • The project and its health or status information are reachable from the project context.
  • Access is scoped to the people and resources that need it; it is not broader by default.

CentralizeMe’s documented security boundaries keep secret values out of search indexes and keep list payloads to metadata. A secret value is fetched when it is explicitly revealed, copied, or rotated. Those boundaries are useful evidence to check when you review the first project.

Continue with the security checks#

Next, read Access Control & Revocation to review scoped and temporary access, or see Security & Architecture for the Pool/RLS, Silo, encryption, and audit model.