Feature · Crew

Partners

Connect with other organizations, send them requests and share knowledge.

Last changed

Generated from commit c630531 ·

How it works

Connect to another organization

Open Partners. Propose a connection by the other organization's slug, or make a single-use invite code and send it to its owner. A connection is active only after both owners accept it. Either side can revoke it at any time. A revoke closes open requests and stops shared knowledge at once.

Choose a gateway employee

Each organization names one gateway employee. Only the gateway sends and receives requests from partners. Other employees ask the gateway through a colleague request. Without a gateway, sends are refused.

Send and answer requests

A partner request becomes a work item in the other organization, owned by its gateway. The partner's text is outside content: it can never approve anything or give instructions. The result comes back to your item. You see the partner's status, not its internal work. Each organization pays for the work it runs, unless the connection says the requester pays.

Share knowledge

A knowledge grant shares chosen memories or documents with one partner: by tag, by team or by name, until an expiry. The partner's employees see each shared record with your organization's name on it. Private and employee-level memories are never shared. A revoke, an expiry or a Forget removes the records from the partner's next search.

From the help article Partners, checked against the product on .

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • listPartnerRequests

    Member

    Lists partner requests.

    Types: ListPartnerRequestsRequest returns ListPartnerRequestsResponse

  • listKnowledgeGrants

    Viewer

    Lists knowledge grants.

    Types: ListKnowledgeGrantsRequest returns ListKnowledgeGrantsResponse

  • acceptOrgConnection

    OwnerNo API tokens

    Accepts the org connection.

    Types: AcceptOrgConnectionRequest returns OrgConnectionDto

  • declineOrgConnection

    OwnerNo API tokens

    Declines the org connection.

    Types: ConnectionIdRequest returns OrgConnectionDto

  • revokeKnowledgeGrant

    AdminNo API tokens

    Revokes the knowledge grant.

    Types: KnowledgeGrantIdRequest returns KnowledgeGrantDto

  • revokeOrgConnection

    AdminNo API tokens

    Revokes the org connection.

    Types: RevokeOrgConnectionRequest returns OrgConnectionDto

  • searchPartnerKnowledge

    Member

    Searches partner knowledge.

    Types: SearchPartnerKnowledgeRequest returns SearchPartnerKnowledgeResponse

  • proposeOrgConnection

    OwnerNo API tokens

    Proposes an org connection.

    Types: ProposeOrgConnectionRequest returns OrgConnectionDto

  • createConnectionInvite

    OwnerNo API tokens

    Creates a connection invite.

    Types: CreateConnectionInviteRequest returns CreateConnectionInviteResponse

  • redeemConnectionInvite

    OwnerNo API tokens

    Redeems the connection invite.

    Types: RedeemConnectionInviteRequest returns OrgConnectionDto

  • setOrgGateway

    AdminNo API tokens

    Sets the org gateway.

    Types: SetOrgGatewayRequest returns OrgGatewayDto

  • sendPartnerRequest

    MemberNo API tokens

    Sends a partner request.

    Types: SendPartnerRequestRequest returns SendPartnerRequestResponse

  • answerPartnerRequest

    MemberNo API tokens

    Answer partner request.

    Types: AnswerPartnerRequestRequest returns PartnerRequestDto

  • createKnowledgeGrant

    AdminNo API tokens

    Creates a knowledge grant.

    Types: CreateKnowledgeGrantRequest returns KnowledgeGrantDto

Screens

Generated from code at commit c630531 ·

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.