Customer Credential Request Starter Kit

A procedure and six messages for an authorized support or onboarding task. Use your organization's approved collection mechanism. No CredenShare purchase is required to use the general guidance. Creating CredenShare Secure Requests requires a Business or Enterprise plan; first-time Business subscribers can start a 14-day free trial. The submitter needs no paid plan; sign-in depends on the request settings below.

The working rule
The conversation coordinates the task. The approved collection route carries the credential. A named system owner decides who may use it and when that access ends.

1. Ask whether the credential needs to move

Start with the task, not a request for a password. Prefer a named invitation, delegated role or a narrowly scoped temporary token when that can achieve the same result. Do not request a person's primary password, recovery code or broad production administrator credential simply because that is convenient. [G1]

Agree the task, environment, privileges, authorized contact, receiving operator, storage and access end condition. A ticket number is context, not approval.

2. Follow one complete collection process

3. Know which link you are sending

With CredenShare Secure Requests, send the Collect link for submission. Keep the Access link private: it carries the decryption key. Save it somewhere durable before you close the creation screen. Without it, responses can be read only in the browser that created the request or on a device activated for zero-knowledge custody. On any other device, paste it into the request's submission viewer to read responses. Never send it to the submitter or forward it to colleagues.

A submitter needs an account only when the creator requires sign-in, or when a request created through the API requires two-factor authentication. [C1]

Keep secrets out of this kit, screenshots, email replies, ordinary tickets and AI prompts. A live Access link is sensitive access material too. Follow stricter organizational or customer requirements where they apply.

Send the request and acknowledge receipt

Copy-ready wording. Replace every bracketed field before sending. Choose only the information needed for the agreed task. Use your normal organizational signature. These are task messages, not a marketing sequence.

Initial request

Reminder for an agreed, outstanding request

Use this only while the request is still expected and appropriate. Do not turn it into an indefinite follow-up sequence. Confirm the submission route is usable before directing the customer back to it.

Receipt acknowledgment

Receipt is not validation. Use "received" only after the authorized operator confirms receipt. Do not say "working" or "verified" until an appropriate authorized check has actually passed.

Handle corrections and closure

A credential arrived in the ticket or email

Do not copy the value into replies or diagnostic tools. Follow your incident procedure, coordinate containment with the owner and consider service dependencies. [G1]

A correction is needed

A timeout does not establish an invalid credential. Describe the observed problem, not an assumed cause.

The task is complete; source access needs closure

Check the two lifetimes before closing a request

CredenShare documents the form's scheduled end separately from the lifetime of submitted responses. Using Expire request now destroys every submission's content at once; the submission records stay as an audit trail, but their content cannot be recovered. Before you use it, open each response you still need in the submission viewer and move the value to its approved protected destination. The request page's export cannot decrypt end-to-end encrypted submissions, so do not rely on it as a copy. Never copy credentials into this kit or the ordinary work item. [C1]

Use disposable data for demonstrations; never a customer's live credential.

A worked example you can reuse

Fictional teaching example. No real customer, credential or test result is represented.

An onboarding team must verify a staging connection. The customer authorizes a temporary read-only integration token rather than providing a personal administrator password.

Configure your first real request

For this example, consider case reference, environment, scoped integration credential, and access end condition. Remove information already known or unnecessary. Do not collect extra credentials "just in case."

Agree recipient verification, form lifetime, response lifetime, operator access and absence coverage. Create the request from the account that will receive the value. Only that account can read the request's submissions; team owners and admins cannot, and reading cannot be delegated. Plan for absence before you create the request: if the intended receiver may be unavailable, have someone who will be available create it from their own account, or use another approved workflow. Never use a shared login.

Confirm the procedure with a disposable rehearsal

Use TRAINING-NOT-A-REAL-SECRET in a nonproduction exercise. Check submission, authorized retrieval and the receipt message. Rehearse an expired request without weakening the process. The operator should explain the next safe action, not merely open a page.

If you cannot establish the required operator access, recipient restrictions or continuity route, pause the request and choose an approved alternative. Do not share a personal account to bypass the problem.

References and scope

[C1] CredenShare: Secure Requests. Product-specific link, plan and lifecycle details were checked against the CredenShare documentation and updated on 2 October 2026. Product behavior can change; confirm current behavior in the documentation before relying on a particular control.

[G1] OWASP: Secrets Management Cheat Sheet. Background on least privilege, lifecycle and exposure response. The operating procedure, examples and messages here are CredenShare-authored guidance, not requirements issued by OWASP.

This resource is not a personalized assessment, a certification or a promise that all external copies have been removed. Adapt the wording to the customer's approved access and records processes.