Skip to content

Document v2 invitation profile limits and guarded creation #124

Closed as not planned
Closed as not planned
Document v2 invitation profile limits and guarded creation#124

Description

@fluxis
fluxis
opened on Oct 8, 2026

Native API v2 can bind an account’s initial profile limit to its invitation and preserve an existing pending invitation when an integration requests non-replacing creation. The manual update waits for Silo-Server/silo-server#2089 to merge.

Pages to update:

  • Invite people and manage accounts (src/content/docs/docs/running-a-server/accounts.md, /docs/manage-accounts): explain that API-created invitations can carry the initial household profile limit. No new web invitation-editor control is added.
  • Use the API (src/content/docs/docs/developers/api.md, /docs/api): document capability discovery, optional positive max_profiles, and replace_existing: false, which returns conflict without replacing another pending invitation. Omission retains the current defaults: five profiles and replacement enabled. Resend carries the bound cap; rollback refuses while a capped invitation can still be claimed.

Apple/Android and Jellyfin need no new invitation-management surface. Coordinate omission/default wording with the profile-inheritance work tracked in #70 and Silo-Server/silo-server#1801 if it merges first.

AI disclosure

  • Harness: OpenAI Codex with multi-agent delegation.
  • Tools: Codex tools, GitHub CLI, repository and website source review.
  • Model: gpt-6.1-sol (configured Codex model; exact runtime identifier is not separately exposed).
  • Involvement: AI-generated; human review pending.
  • Review: checked the current manual pages, server contract and independent transactional review; native HTTP, database, rollback and desktop/phone evidence are recorded in the server PR.

Activity

  1. zZebrahz commented on Oct 10, 2026

    @zZebrahz
    zZebrahz
    on Oct 10, 2026
    Contributor

    This is blocked: there's nothing to document yet.

    Silo-Server/silo-server#2089, which added max_profiles and replace_existing to v2 invitations, was closed without merging on 8 October, and no other pull request picks it up. On silo-server main (9d37930c6), invitations have no profile limit field. An account created from an invitation still starts with the server's default profile limit, and creating a new invitation for an address still replaces its pending link. max_profiles exists only on the account create and update endpoints, and nothing matches replace_existing.

    Silo-Server/silo-server#1801 (access-group profile limits, still open) doesn't change invitations either. #101 covers its docs.

    I suggest closing this as not planned. If invitation profile limits come back in a new server PR, we can reopen it or open a new issue that links to that PR.

  2. zZebrahz
    closed this as not plannedon Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions