Skip to content

Access controls

Make agreement access specific to the work people need to do.

Agreement access is not a single on or off switch. Inklok uses organization roles, workflow participation, and cryptographic access for protected values to help keep access aligned with the work each person is authorized to perform.

Use roles in the workflow

A template can define roles such as author, reviewer, or signer. The agreement workflow uses those roles to make responsibilities and routing explicit.

Membership is not the same as historical access

A newly added organization member does not automatically receive access to old protected values. Historical protected access requires an applicable previously issued or separately authorized cryptographic grant, in addition to an eligible role.

Keep authorization and decryption distinct

Authorization is necessary but it is not itself a decryption key. Inklok deliberately separates service authorization from the cryptographic path used for protected signing values.

Example: separate preparation, signing, and oversight

A sender may prepare an agreement, external participants complete assigned signing steps, and a permitted organization member may need visibility into workflow details. Those tasks require different access. Review the permissions available to each role instead of sharing a sender account to make everyone see the same screen.

Metadata access is not decryption access

A colleague may be authorized to view an agreement's status without possessing the cryptographic material for protected signing values. Access also depends on when the person became authorized. Test the specific workflow and role in the product rather than assuming organization membership grants unrestricted access to historical protected data.

Questions

Questions about access controls

Can a new organization member read every old agreement?

Not automatically. Historical protected access requires a separate applicable cryptographic grant as well as the appropriate authorization.

Can permissions control workflow activity?

Yes. Workspaces and workflows use roles to help control who can prepare, send, review, manage, and participate.

Does Inklok claim identity verification?

No. Permissions and workflow roles are not an identity-verification product.

Keep exploring

Related Inklok resources

Agreement Permissions and Participant Access | Inklok