Blame

94c84c Anonymous 2026-06-20 21:50:43
Add AeThex documentation page
1
# Linked Accounts
2
cf0a5e Anonymous 2026-06-23 03:31:08
3
Linked Accounts connect a Passport identity to external accounts, communities, services, games, and tools.
94c84c Anonymous 2026-06-20 21:50:43
Add AeThex documentation page
4
cf0a5e Anonymous 2026-06-23 03:31:08
5
<div class="docs-section-heading">
6
<h2>Why linking matters</h2>
7
<p>Linking lets AeThex recognize the same person across multiple ecosystem surfaces.</p>
8
</div>
94c84c Anonymous 2026-06-20 21:50:43
Add AeThex documentation page
9
cf0a5e Anonymous 2026-06-23 03:31:08
10
A linked account should never replace [[Passport]]. Passport remains the primary identity layer; linked accounts add context for integrations such as Discord, game platforms, developer tools, or partner services.
11
12
## Common linked account types
13
14
- Discord or community accounts.
15
- Git or developer platform accounts.
16
- Game or experience accounts.
17
- Organization-managed service accounts.
18
- Support or ticketing identities.
19
20
## Linking flow
21
22
1. User starts from Passport or an integration surface.
23
2. External service proves account ownership.
24
3. AeThex records the connection and metadata.
25
4. Permissions are evaluated separately through [[Permissions]].
26
5. Users can review or disconnect links where supported.
27
28
<div class="docs-grid">
29
<a class="docs-card" href="/Passport">Passport</a>
30
<a class="docs-card" href="/Authentication">Authentication</a>
31
<a class="docs-card" href="/Permissions">Permissions</a>
32
<a class="docs-card" href="/Security">Security</a>
33
</div>
34
35
> [!WARNING]
36
> A linked account proves account control, not automatic authorization. Always check roles, scopes, and project access separately.