Executive search
Recruiting software integrations: review the permission before the connection
Map a recruiting integration's task to its actual access, acting identity and destination. Includes a filled decision record, current provider examples and a practical exit check.
A partner wants a draft for the weekly client call. The proposed connector can also change candidate records and send messages. Before connecting it, the firm's operations lead needs an answer to a specific question: can this preparation task run within the access the firm is willing to grant?
Review the capability, identity and destination together. A permission label explains part of the access; the role, plan and configuration determine how it applies. The following method helps a buyer make that decision without assuming that every connection to the same provider behaves alike.
TL;DR
- Define the task and the records it needs before reviewing the connection request.
- Distinguish reading, drafting, changing records and sending messages.
- Verify the acting identity and the result's effective audience.
- Record unsupported boundaries as open questions, with a workable fallback and an owner.
A filled permission decision record
This is a fictional buying exercise, not a report of a tested integration. A search firm wants an internal preparation note for mandate M-204. It has three synthetic research notes, an agreed client brief and an existing destination folder restricted to the assignment team.
| Review item | Proposed decision | Evidence still needed |
|---|---|---|
| Outcome | Draft an internal briefing from the four selected inputs. | Demonstrate that the chosen input route uses those inputs as intended. |
| Source access | Use selected files for the initial exercise. No mailbox connection is needed. | Confirm the product's actual upload, storage and deletion behavior. |
| CRM reads | Optional for a later test; the initial task does not need database access. | Identify the exact records, fields, role and supported read boundary before adding it. |
| CRM writes | Excluded from the initial task. | Demonstrate that the proposed configuration cannot perform writes; a prompt saying “do not write” is insufficient evidence. |
| External messages | Excluded. The consultant will review the note in the existing process. | Confirm whether send tools are available and how they are controlled. |
| Destination | Assignment-team folder; no client-facing copy yet. | Check actual folder membership and any inherited or linked access. |
| Decision | Proceed only with a supported input-and-draft route within these limits. | If the product requires broader capabilities, keep the connection pending and evaluate the manual route. |
| Owner and exit | Operations lead owns configuration; assignment consultant owns factual review. | Record how to stop future access and what happens to previously retained material. |
Add the provider's exact permission wording, acting account, plan, configuration date and observed test result when they are known. Until then, this is a proposed boundary. Do not relabel a hoped-for control as demonstrated behavior.
Start with the work that creates the administrative burden
Preparing a brief from selected assignment notes is different from continuously searching a mailbox. Updating a reviewed field is different from autonomous database maintenance. The research-note guide can help identify the evidence the output actually needs.
Ask what the connection is meant to improve: finding the right source, capturing it accurately, avoiding repeated copying, or returning an accepted correction to the record. If an existing Claude workflow already produces an adequate draft, compare the remaining capture and administration work before adding a connector. Include setup, ongoing review, software cost and privacy requirements in that comparison; this article does not establish that Laisy or another tool is a better fit.
A manual input and reviewed handback can answer whether the output is useful. It does not establish that a future automatic connection will have the required controls. Keep those two findings separate.
Translate access wording into operations
Copy the requested permissions into the review record and identify the operations they allow. “Calendar access” is too vague to distinguish viewing events from changing them.
Google's linked-app guidance distinguishes access to particular services and levels such as viewing or managing data. It also explains that removing access stops further access but may leave data already held by the app developer. The review therefore needs both a future-access question and an existing-copy question.
For each operation, identify the records covered and the reason the task needs it. If the requested scope is broader, ask for a supported narrower configuration or another route. The supplier may have a technical explanation; that explanation still needs to be weighed against the firm's intended use.
Establish whose identity performs the operation
Microsoft's permissions-and-consent overview distinguishes delegated access on behalf of a signed-in user from app-only access under the application's identity. In delegated access, both the client application and the user need authorization. The label alone does not identify which records a particular configuration can reach.
Record the actual user, application or service connection and who maintains it. A partner's personal connection may behave differently from a shared service identity. Ask what happens when that person changes role or leaves, and who can inspect or revoke the access.
An administrator's technical grant also does not specify every business action the firm wants the tool to perform. Keep the authorized task explicit, especially when the same integration can both retrieve evidence and alter records.
Check the product's role and plan constraints
A concrete provider example makes this review less abstract. Recruit CRM's MCP documentation, checked on 3 November 2026, describes OAuth connections scoped to the user's role. It distinguishes Read Only access from Read & Write access.
The same documentation says Account Owner and Admin roles always have Read & Write MCP access. It also says only those roles can use MCP on the Pro plan. A buyer seeking a read-only pilot should therefore verify the actual role and plan instead of assuming that an administrator connection can simply be switched to read-only. This is documentation evidence, not our test of a Recruit CRM account or a recommendation to change plans.
Capture the discrepancy as a decision: “Our proposed task excludes writes; this configuration's documented role includes them.” The next step is a supported alternative, supplier clarification or a different bounded task. A written instruction to the model does not prove a technical access boundary.
Inspect where the result becomes visible
Correct source access does not establish appropriate destination access. An internal note placed in a broadly shared CRM object or folder can reach a different audience from the original files.
Attio's object-access documentation describes access based on the most permissive applicable workspace, team or member grant. A narrower individual setting cannot override a broader workspace grant. This is one product's access model; use the destination's own documentation and actual configuration for your review.
Ask an intended reader and an intended non-reader to test the result with synthetic material through the normal authorized process. Record what each can view and change. A filtered screen or hidden field is not evidence that the underlying content is protected from that role.
The client-update workflow supplies a useful separate decision: an internal draft can be factually accepted while its client-facing version and recipients remain unapproved.
Test the failure that would cause a duplicate action
For an integration that will eventually write or send, ask how the operator checks an uncertain result. A timeout does not tell them whether the operation happened. The documented recovery path should establish the destination state before repeating a possible write or communication.
Use an appropriate controlled environment and synthetic material; do not manufacture failures against production records merely to complete a checklist. If only the file-based preparation route has been evaluated, record write recovery as untested.
The handover guide helps preserve the last verified state when another person resumes. Record the operation, target, observed result, remaining uncertainty and next permitted action. “Try again” gives the next operator none of that context.
Agree the fallback and continuing owner
Decide how the task proceeds when authentication expires, a permission changes or the connection is unsuitable. The fallback may be selected manual inputs, an export-and-review step or a pause. It should preserve the same data and audience limits.
For the exit, distinguish stopping future access, deleting retained copies and correcting changes already made in the destination. Obtain the relevant product evidence for each. Where removal requires a supplier request, record its owner and the confirmation the firm expects.
Revisit the decision when the acting identity, data scope, action capability, plan or destination audience changes. The pilot-success criteria can keep the evaluation bounded to one useful task while including configuration and review effort. A successful connection is only one part of that result.
Frequently asked questions
Does signing in authorize every connected feature?
The actual permission request, role and organizational decisions determine the access. Inspect those and any later requests for additional capabilities. A familiar sign-in screen does not describe the whole workflow.
Is delegated access always the right choice?
No single access model fits every task. Use the provider's documented model and the responsible administrator's review to establish the identity, scope and maintenance arrangements the task requires.
Can a read-only connection still expose information elsewhere?
Reading and copying can place information into another system or output. Check that destination's audience and retention as well as the source permissions.
What if the requested access is broader than the task?
Keep the connection decision open. Seek a supported narrower configuration, evaluate a manual route or decline the connection. Record the specific mismatch so the next review can resolve it.