Join a Space
Review the proposed work, authorize your contribution, and choose what may be released, without joining another organization’s account.
Another organization has invited you to contribute to its work. You join under your own identity, keep your own credentials and signing keys, and decide how your own assets are used. This guide follows the vendor in the vendor-diagnostics example, who contributes a diagnostic program to a customer's Space.
Accept the invitation
Sign in with your own account, or your organization’s team account, and accept the invitation. Accepting lets you participate in that Space. It does not give you access to other participants’ inputs, and it does not give the sponsor any authority over yours. You do not need a paid plan to participate; the sponsoring organization pays for the execution it sponsors.
What am I authorizing?
Review the operation profile before you authorize anything. It names the accepted program, required roles and inputs, and the outputs each recipient may receive. Your authorization covers your own contribution to that named work. It does not cover a different profile, a different input or anything beyond the task.
Who receives the output?
The profile lists each permitted output and its recipients. You authorize the release of results that depend on your contribution. In the example, the customer’s assurance team receives the findings and you receive a narrower service summary. A recipient cannot receive more than the release rules allow.
What remains private?
You encrypt your input before contributing it. Your key-access policy permits decryption inside the accepted confidential runtime for the authorized operation. Other participants, their agents and Standard's operators do not receive your private contents through the normal path. Being in the same Space does not let anyone read your input. See Inputs and permissions.
Can routine work proceed automatically?
Yes, within the bounds you set. A bounded standing permission lets routine runs of the same work proceed without a new approval each time. A new scope, such as a new input, a different program revision or a new recipient, needs your fresh authority before it continues.
What happens when I decline?
The operation does not run, or the result is not released, without your authorization. The requesting client reports that your authority is outstanding; nobody else can supply it for you. A request outside your standing permissions always comes back to you.
Connect your own agents
You can connect your own agents or services through MCP, the SDK or the CLI. Connecting identifies the caller; it grants no authority over other participants’ assets. See Connect.