Describe the account, its owner, and its reviewer. Makeform creates structured intake for employee, customer, contractor, or privileged accounts.
Send account requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, customize it, or send it to the Makeform builder. Samples show structure, not live results.
Audience
Managers requesting access for new employees
Format
Provisioning request with role-based access details
Prompt size
246 chars
Example form structure
Provisioning request with role-based access details
Employee identity and contact details
Role, manager, and start date
Which systems and roles are needed?
Dates and business reason
Manager confirmation
Suggested routing tags
Employee access
Customer accounts
Privileged review
Ask for a named manager, owner, or reviewer so the request has a routing contact.
Step 1
Identify
requester, account holder, and sponsor
Step 2
Scope
account type, systems, role, and duration
Step 3
Review
owner checks details and supporting files
Step 4
Route
complete request reaches the right queue
Why structured requests matter
Email often omits the owner, role, expiry, or reviewer. A focused form gathers them before routing.
Separate the requester, account holder, reference, sponsor, and contacts.
Use system lists, roles, dates, and reasons to define the request.
Tag each request type and send it to its owning team.
Common account workflows
Choose a workflow, then add your real systems, account types, reviewers, and documents.
Capture manager, start date, department, applications, roles, and onboarding reference.
Collect applicant, product, intended use, users, branch, and documents for review.
Ask for owner, scope, task, duration, ticket, and acknowledgment.
Require a sponsor, project, permissions, and access end date.
Build the workflow
Generate fields, add your catalog and branches, then connect reviewers.
Name the audience, account types, identity fields, systems, roles, documents, and reviewers.
Edit dropdowns, products, departments, branches, permissions, and document instructions.
Show business, remote-access, and expiry fields only when relevant.
Route submissions to inbox, Slack, Sheets, or Zapier without presenting receipt as approval.
Form vs email vs generic ticket
Good intake captures identity, scope, ownership, dates, and supporting details consistently.
Field guide
Use these six sections, then apply your organization's identity, notice, review, and approval procedures.
Requester and account holder
The requester and account holder may differ. Separate fields identify who asks, who receives access, and who sponsors it.
Account type and destination
Start with the product, application, environment, or service. A controlled list can also determine later questions.
Role and access scope
Ask for a named role that supports the work. Offer known options and a description when none fits.
Identity and documents
Request only process-relevant records. Label uploads and avoid implying that a file automatically verifies identity or opens an account.
Timing and ownership
Dates make provisioning schedulable. Ownership identifies who answers questions and reviews scope.
Reason and acknowledgment
Record the reason and relevant acknowledgments. State that submission begins review rather than granting approval.
Related tools
Use focused forms for customer, privileged, API, onboarding, service, or self-registration workflows.
Collect customer products, applicant details, intended use, and documents.
Open toolCollect privileged roles, tasks, duration, owners, and references.
Open toolAsk for environment, use case, scopes, data, owner, and lifecycle.
Open toolBuild self-registration when users create their own profile.
Open toolGather people, dates, equipment, payroll, and orientation details.
Open toolRoute accounts with other internal technology requests.
Open toolFAQ
Answers for IT, operations, managers, and financial-service teams.
It is structured intake used before account review or creation. It identifies the requester and holder, account or system, requested role or product, dates, reason, and supporting details. IT provisioning and customer intake should use different fields and review paths.
Include requester, account holder, manager or sponsor, department, start date, applications, role per application, reason, needed-by date, and temporary-access expiry. Add owner, ticket, remote-access, and acknowledgment fields when relevant. Always state access scope, even when referencing another user.
Ask for personal or business type, product, applicant identity and contacts, address, intended use, expected activity, authorized users, and branch. Request only documents required by the bank's process. State that submission starts review and does not open or approve an account.
Yes. Use an account-type choice and conditional logic. Employee questions can cover manager and department; contractor questions can require sponsor and expiry; business-customer questions can cover organization and authorized users.
Ask for environment, exact permission, supported tasks, owner, reviewer, ticket, and temporary or standing duration. Require an expiry for temporary elevation. Keep privileged requests distinct so the organization's review procedure can be applied.
No. The form collects and routes information for review. Confirm that the request was received or sent for review, then communicate approval, questions, or provisioning status through your designated process.
Yes. Makeform provides unlimited free forms and responses, including generating, editing, publishing, and using the form without a response cap. The paid tier removes the Makeform badge.
Submissions can reach your Makeform inbox, Google Sheets, Slack, or Zapier. Route employee access to IT, customer intake to branch staff, and privileged access to the system owner. Keep decisions in your designated review workflow.
Replace incomplete account-request emails.
