Understand approval-body destinations for shared work¶
An approval body can supply a receiving destination for work shared between connected workspaces. The destination identifies a responsibility: the committee as a whole, its chairperson or its signing authority. The people currently holding that responsibility determine who receives the work.
This page explains the implemented routing rules. Use the Share work guide for the inspected design steps and the decision guide for rerouting. The frontend remains under development; source support does not establish that every destination or journey is connected in your environment.
Choose the responsibility, then check the people¶
| Destination | Who the service resolves | What that does not establish |
|---|---|---|
| Committee | The body's currently effective members, including members without voting or signing access | A vote, an approval, quorum completion or a signature |
| Chairperson | The currently effective chairperson | Signing access or permission to complete every business action |
| Signing authority | Current direct signers and eligible people signing through a delegation | That a document was signed, a decision was approved or every recipient may perform every action |
The destination choices currently supplied to shared-work authoring include committee and signing-authority options. Chairperson resolution is supported internally, but this options source does not offer a separate chairperson choice. Do not infer a missing or hidden control from that internal capability.
For example, a purchasing committee has five effective members, three voters and one direct signer. A committee destination can resolve to all five members. A signing-authority destination can resolve to the direct signer and an eligible delegate. The quorum remains a separate voting rule. Sending the package to either group does not complete the purchasing decision.
The sender should choose the responsibility agreed with the receiving workspace. If two bodies have similar names, use the readable reference and description and confirm the intended owner. Do not choose a different body just because it appears in the list.
Why a body appears in the choices¶
The body must be active. A committee option requires at least one effective member; a signing-authority option requires at least one effective direct signer. Future members do not count before their start, and ended or inactive members do not supply current authority.
These option checks do not require the body to have a chairperson or enough voters to meet its quorum. A body can therefore appear as a destination while its administration page still shows readiness warnings. Review the body's active state, dates and readiness for the intended work instead of treating an offered destination as proof that the whole approval process can proceed.
The signing-authority destination can resolve to more people than the displayed direct-signer count. A delegation contributes only while it and its originating signing membership are effective. For the protected organization-head body, the delegate must also have effective membership. Several authority entries for the same person produce one recipient in the routing result.
Resolution uses current authority¶
Available choices are a current lookup. The people are resolved again when the owning work process uses the destination. A membership expiry, chairperson change, delegation change or body deactivation between those stages can change the recipients or make resolution fail.
This route does not freeze the membership at the time the sender first opened the form. Nor does it offer a historical or future-date recipient selection through the current governance resolver. For an investigation, use the exchange's retained evidence and activity history; the body's current list is not a complete record of who received an earlier package.
Changing a chairperson has wider membership consequences: the old chair's membership and the incoming member's previous membership are closed before the new chair membership is created. Delegations remain tied to their original membership. Review the chairperson-change guidance before relying on an existing destination.
Receiving, access and completion are separate¶
The routing result supplies recipient identities. The owning shared-work process determines participation and checks its own connection, policy, actor and action rules. A routing result alone is not a guarantee that every person can enter the product, view the attached file, accept the exchange, vote or sign.
Likewise, rerouting does not prove that former recipients lost access. The inspected shared-work projection adds newly addressed people while retaining earlier participants. Follow the shared-work participation and decision guidance when a package changes hands. Treat any access-removal requirement as a separate matter for the owning administrator.
Resolve missing or changed destinations¶
| Situation | What to check | Useful next step |
|---|---|---|
| No committee option | Correct receiving workspace, active body and at least one effective member | Ask the receiving administrator to inspect the body and membership dates |
| No signing-authority option | At least one effective direct signer, then any intended delegation | Check signing access and both authority periods; voting access alone is insufficient |
| Choices cannot be loaded | The receiving workspace and the availability of its people and governance directories | Retry loading the choices; do not treat an unavailable list as proof that the workspace has no destinations |
| A previously offered destination fails | Membership, chairperson, delegation or body state may have changed | Refresh the choices and confirm responsibility before submitting again |
| More or fewer people receive the work than expected | Committee membership versus direct/delegated signing authority and the time of resolution | Compare the selected responsibility with current authority and the exchange's recorded result |
| Submission times out | The final result of the original attempt | Check the existing sent/received item before repeating the operation; a timeout does not prove that nothing was saved |
For support, provide the receiving workspace, readable body/reference, selected responsibility, approximate time and the last confirmed result through the approved support channel. Avoid broadening a body's membership or signing rights merely to bypass a routing error. Confirm the intended business authority first, then verify the resulting shared work separately.