Contacts
A contact is one account's public name for another account, and this page explains how you follow a person, join a site and become a member, and why none of these gives a permission.

A contact is a public address-book entry. It says: "account A calls account S by this name". It also carries two flags. For example, Alice publishes a contact that names Bob's account "Bob from work".

A contact gives no permission. The daemon never looks at a contact when it decides what a key may write or read.

This page explains what contacts are for. The contact type page lists the fields.

Following, joining and membership

The Seed apps use the two flags in subscribe to record how you relate to an account:

    site: true means "I joined this site".

    profile: true means "I follow this person".

    A contact with neither flag counts as a plain follow.

To join a site, you publish a contact with site: true. To leave, you remove the flag or the contact. The People and Members views of a site list the accounts that published a joining contact. A writer who joins appears as a member with their role. Membership gives no permission.

The indexer does not check who signs a contact for whom. The daemon's own contact RPCs do check the writer rule first. The daemon never turns a contact into a sync subscription. The apps do that. See Contact and Contact subscription.

Identity and visibility

A contact is a snapshot blob: each edit is a whole new copy of the record. Its record id is <account>/<tsid>. A contact with an empty subject is a tombstone, which marks the contact as deleted. Contacts are always public, and the daemon indexes them for search. So a name you gave someone shows up when you search for it.

Contacts and trust

No code path lets one user's contacts change what a third party may read or write. The grants that do carry authority are capabilities.

Working with contacts

You can create and remove contacts in four ways:

    In the CLI: seed-cli contact create --subject <uid> --name "…" and seed-cli contact delete <id>.

    In the SDK: createContact and deleteContact.

    In the Seed app: the Join and Follow buttons.

    From an agent: the write actions contact.create and contact.delete.

A contact made with the CLI has neither flag, so it counts as a plain follow. Only the apps and the SDK's createContact can set subscribe.site or subscribe.profile.

On the Seed API, GET /api/AccountContacts?__value=<uid> and GET /api/SubjectContacts?__value=<uid> list contacts by owner and by subject. GET /api/ListDocumentCollaborators?targetId=… joins grants and joining contacts into the one list the app shows.

See also

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Attributes
name
Contacts
summary
A contact is one account's public name for another account, and this page explains how you follow a person, join a site and become a member, and why none of these gives a permission.