Skip to content
Help Center
Submit a request Sign in

Control who can close Cases without blocking everyday support work

The Close Cases permission controls whether an agent can complete a Case through the closure action. Use it when a support process needs a designated person to confirm resolution, for example while new agents are learning or when a specialist must validate a complex B2B incident. Agents can continue the other work their role permits. A successful process combines the permission with a clear handoff so customers are not left waiting for someone who has authority to close.

At a glance

For: support managers and administrators responsible for agent roles and resolution quality. Applies to: Supportbench Core.

Start here: Settings → Roles → open the role → Permissions

Decide when a closure restriction helps  ·  Check prerequisites and the affected role  ·  Remove or restore Close Cases  ·  Verify both the restriction and the work that must continue  ·  Give the reviewer a useful closure request  ·  Troubleshoot closure problems

Decide when a closure restriction helps

SituationUseful processTradeoff to plan for
New agents need help assessing resolutionLet them investigate and prepare the resolution, then hand it to an authorized reviewer.Provide reviewer coverage and coaching; do not create an unattended queue of completed work.
A complex customer issue needs specialist confirmationHave the specialist verify the technical result and an accountable person confirm the customer follow-up.A technical fix alone may not complete every account-specific obligation.
A service process requires a designated closerRestrict the role and document the required resolution evidence.The permission itself does not build an approval workflow or assign a reviewer.
A single agent closed one Case incorrectlyReview the individual incident and training need before changing a shared role.A role change can affect everyone assigned to it, including people who already follow the process.

Treat a closure restriction as a process design decision. If experienced agents are expected to own Cases end to end, removing their close authority may add delay without improving quality. State which risk the restriction addresses, who can close, and how long a ready-for-review Case should wait. These are operational recommendations, not default Supportbench rules.

Check prerequisites and the affected role

  1. Ask an administrator with Administer agent roles permission to make the change. An agent who can work Cases does not automatically have authority to change roles.
  2. Identify the role assigned to the affected agents. Review who else uses that role before editing a shared permission.
  3. Confirm that the intended closer can access the relevant Cases and has the permissions needed for closure. Close authority does not grant access to every customer or Division.
  4. Define what the investigating agent must provide: the verified resolution, remaining customer obligations, linked work that still matters, and the proposed next step.
  5. Agree how the handoff will be visible, for example an assigned Case task or an internal discussion mentioning the responsible reviewer. Keep an explicit owner and due time; a mention alone is not a promise that the work has been accepted.
  6. Choose an approved sample Case for verification. Avoid closing a live customer Case simply to test a permission.

Remove or restore Close Cases

  1. Open Settings → Roles and open the role you intend to change. Confirm the role name before editing.
  2. Open the Permissions tab. Use the permission search to find Close Cases.
  3. Clear Close Cases to remove closure authority from that role. Select it when the approved process requires restoring that authority.
  4. Review the other selected permissions and the role’s Division scope. Change only the controls required for this decision. Do not remove ordinary editing or broaden customer access as a workaround.
  5. Save the role. Reopen it and confirm the saved Close Cases selection.
  6. Have a representative affected agent refresh their session and repeat the approved verification workflow. If the result does not reflect the saved role, check the actual assigned role and current session before making further changes.

What this change controls

Core checks closure authority on the server, including the closure and bulk-close paths. A normal status-field update cannot bypass the dedicated closure command. Removing Close Cases does not, by itself, remove all Case editing, customer replies, or reopening rights. Those actions depend on their own permissions and the Case context.

Verify both the restriction and the work that must continue

CheckExpected resultIf the result differs
Saved roleClose Cases is selected or cleared as intended.Reopen the correct role and verify the save before testing agents.
Representative restricted agentThe agent cannot complete an authorized sample through the closure action.Check actual role assignment and session refresh. Record the Case ID and attempted action for the administrator.
Ordinary permitted workThe agent can still perform the intended investigation, internal updates or customer communication allowed by the role.Review the separate permission or access boundary; do not assume Close Cases controls all actions.
Authorized closerThe designated closer can access the sample and complete the appropriate closure process.Check Case visibility, closure permission and required closure information.
Bulk workAgents cannot use bulk close to evade the closure restriction.Review the selected IDs and role with the administrator; do not test on unrelated live Cases.
HandoffThe reviewer can find the request, understand the evidence and identify the next action.Improve the task/discussion and ownership process rather than broadening access.

Record the saved role, representative agent, sample Case and result in the team’s change record. Keep credentials and private customer content out of screenshots or shared training material. A role screen showing a checkbox is configuration evidence; the representative workflow confirms whether the intended agent experience is working.

Give the reviewer a useful closure request

A customer reports a recurring equipment issue. The investigating agent confirms the workaround, identifies the affected asset and checks whether the same problem remains open elsewhere for that Company. Because the agent’s role cannot close Cases, they record an internal resolution summary and assign the agreed reviewer a clear next action.

  1. State what failed and what was done, with the relevant evidence or customer confirmation.
  2. Identify unresolved commitments, linked Cases or customer-specific follow-ups that should prevent closure.
  3. Specify the decision needed from the reviewer and when the customer expects an update.
  4. Keep the Case owner and customer communication responsibility explicit while review is pending.
  5. After the authorized closer acts, verify the saved Case status and any required customer communication. A closure state is not proof that every proposed message was sent.

This approach makes the permission useful in B2B work: a reviewer receives enough account context to make a decision without repeating the whole investigation. Measure the time Cases wait for review and the frequency of avoidable reopening to decide whether the process needs more coverage or clearer resolution criteria.

Troubleshoot closure problems

ProblemLikely checks and corrective action
The agent still appears able to closeConfirm the saved role, the agent’s actual assignment and refreshed session. Test the actual closure action on an approved record rather than inferring authority from a visible status label.
The agent cannot edit or reply eitherReview the separate edit/reply permissions and Case access. Removing Close Cases alone does not explain every denied action.
A supervisor cannot find the CaseCheck Division and record visibility and the intended assignment. Closure permission does not grant access to otherwise hidden customer work.
The closer has permission but closure is rejectedCheck required closure information and the current Case state. Permission is necessary but does not waive the closure form’s validation.
Cases sit waiting for an authorized closerReview coverage, reviewer assignment and escalation of overdue review tasks. The permission does not automatically route or approve work.
A Case closed through another processInspect the Case history and the process that performed the change. A restriction on an agent’s direct authority is not evidence that every automation or external actor was disabled.
The team wants temporary access backReview the shared role’s impact before restoring the permission; verify the change with the same representative checks.

Was this article helpful?