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?
Choose a local encrypted-file contribution or a supported connected source. For connected sources, you approve the connection and resource selection, and retain persistent control of keys and API secrets in your own vault or key store. Attested confidential ingress retrieves and validates the authorized material; the operation worker processes the approved inputs. The requesting agent uses references and receives only its permitted result. See Sources and customer vaults.
Can routine work proceed automatically?
Only where you allow it. By default each operation needs your approval when it is requested, and an approval covers that operation only. You can opt in, per host, to a standing permission that repeats one exact task (same inputs, recipients and release rule; no connected sources; at most 100 runs over at most 30 days), and revoke it from the Space page. A new scope, such as a new input, a different program revision or a new recipient, comes back to you 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. Any request your own approval does not cover comes back to you.