Before you start
Use named accounts and confirm the owner's authorisation. Know the shop, environment and duration for which access is needed.
A recognisable example
DYMR asks its agency to investigate a publication problem. The agency receives the necessary shop access rather than the owner's shared password.
Step by step
- Review Team & access and the relevant shop permissions with the owner. Choose the minimum role that supports the agreed task.
- Review Execution & safety for the intended write path. Check whether the action requires review, a capability grant or another explicit authorisation.
- Use the supported workflow and keep its job or publication reference. Record who approved the action and which source result was confirmed.
- After the work, remove temporary or support access and review the log. Revoke obsolete source credentials through the appropriate source settings too.
What you should see
The agency can work within an agreed scope. Removing a person from an organisation does not automatically prove that every separately issued WooCommerce credential has been revoked.
If it does not work
Permission denied? Check the organisation, selected shop, role and action scope. Do not widen access until the reason is understood. If a grant expires, obtain a fresh approved grant rather than bypassing the check.
Menu names and available actions depend on your app language, permissions and connected shop. Screens show the real Daymerce interface with fictional DYMR data; original screen labels are preserved.