# Members

A **Member** represents an identity that can interact with resources within an Organization.

Personal Accounts
Represent **individual users** — developers, administrators, and support engineers.

Identified by a unique **email address**.

Service Accounts
Represent **automated systems or processes** — pipelines, bots, and scheduled workers.

Identified by a unique **name** such as `ci-pipeline` or `deployment-bot`.

Every action performed within an Organization is associated with a Member identity — whether
that action originates from a person using the Synqly management interfaces or from an automated
system interacting with the platform programmatically.

## Why Members Are a Separate Concept

Rather than treating people and automation as fundamentally different actors, Synqly models both as Members. This allows permissions, auditing, ownership, and activity tracking to be applied consistently — regardless of whether the action originates from a human or an automated workflow.

| Actor | Example action |
|  --- | --- |
| Developer | Creates an Account through the Management API |
| CI/CD pipeline | Provisions Integrations automatically |
| Support engineer | Troubleshoots a customer configuration |
| Automation service | Rotates credentials on a scheduled basis |


A consistent identity layer
Although these actors look different, they all operate through the same identity model — enabling consistent permissions, auditing, and activity tracking across the Organization.

Depending on permissions, Members can create Accounts, manage Integrations, generate tokens,
configure Integration Points, and monitor activity.