An agreement connects the parties, permitted purpose, relevant knowledge, and terms of use. It can include a time limit and a price. Keep that record with the activity it authorizes.
Purpose-bound access
Record who may use knowledge, for which purpose, and on what terms.
Make the terms explicit
Limit the activity
A lender may need an affordability assessment, rather than unrestricted access to every financial document. The agreed use identifies the information and actions needed to answer that question.
Authorize a specific collateral question for a named quotation, with permission to retain its answer there. The customer's workspace executes the assessment; the lender receives the scoped result. See how that mortgage quotation works.
Returning a result still discloses information. The agreement and execution boundary determine what is authorized; saying that the source workspace stays with its owner does not mean that nothing is communicated.
Keep the evidence
Connect the use to its agreement and resulting record. Review who acted, under which authority, and what was returned.
Data usage contracts explain offers and product-specific conditions.
Identity and access establishes participants and their powers. Payments and budgets covers financial authorization. The Agreements app is a management experience over these capabilities, rather than a prerequisite for every platform access check.
Developer reference
Technical details
Authorization tuple
Evaluate (principal, resource, action, purpose, grant, conditions) at execution admission. Workspace membership and authority for a specific use are independent inputs; payment authority supplies neither.
Rights descriptions use ODRL concepts: permissions, prohibitions and duties. The supported grant-evaluation scope determines executable checks; vocabulary conformance does not imply a universal legal-policy interpreter.
An affordability Story can authorize an assessment output while denying arbitrary retrieval of source documents. Enforce that scope in the service, bind execution evidence to actor/agreement IDs, and expose only authorized results. Human obligations remain recorded duties where software cannot independently establish their fulfillment.