# Business Central User Access Request Form Template

> Source: https://netray.co/tools/business-central-user-access-request-form-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A fill-in form that records who needs access, which license, role center and permission sets, and who approved it.

## Category

microsoft-dynamics

## Erp

Dynamics 365 Business Central

## Audience

- BC administrator
- Internal auditor
- IT manager
- Controller

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### BC company name

**Key:** bc_company

**Type:** text

**Default:** CRONUS

#### Environment

**Key:** environment

**Type:** select

**Options:**

- Production
- Sandbox
- Both

**Default:** Production

#### Request date

**Key:** request_date

**Type:** date

**Default:** 2026-10-20

#### Request type

**Key:** action

**Type:** select

**Options:**

- New user
- Change access
- Remove access
- Temporary access

**Default:** New user

#### User name

**Key:** user_name

**Type:** text

**Default:** Jordan Lee

#### Work email

**Key:** user_email

**Type:** text

**Default:** jordan.lee@example.com

#### Department

**Key:** department

**Type:** text

**Default:** Accounts Payable

#### Line manager

**Key:** manager

**Type:** text

**Default:** Priya Shah

#### License type

**Key:** license

**Type:** select

**Options:**

- Essentials
- Premium
- Team Members
- Device
- External accountant

**Default:** Essentials

#### Role center / profile

**Key:** role_center

**Type:** text

**Default:** Accounts Payable Coordinator

#### Permission sets requested

**Key:** permission_sets

**Type:** textarea

**Default:** D365 BASIC, D365 PURCH DOC, D365 PURCH POST, D365 VENDOR EDIT

#### Business justification

**Key:** justification

**Type:** textarea

**Default:** New AP clerk responsible for purchase invoice entry and vendor maintenance.

#### Access end date (temporary)

**Key:** end_date

**Type:** date

**Blocks:**

#### Business Central User Access Request

**Body:** Company: {{company}}
BC company: {{bc_company}}
Environment: {{environment}}
Request date: {{request_date}}
Request type: {{action}}

#### User details

**Table:**

**Columns:**

- Field
- Value

**Rows:**

**0:** User name

**1:** {{user_name}}

**0:** Work email

**1:** {{user_email}}

**0:** Department

**1:** {{department}}

**0:** Line manager

**1:** {{manager}}

#### Access requested

**Table:**

**Columns:**

- Item
- Value

**Rows:**

**0:** License type

**1:** {{license}}

**0:** Role center / profile

**1:** {{role_center}}

**0:** Access end date

**1:** {{end_date}}

#### Permission sets

**Body:** {{permission_sets}}

#### Business justification

**Body:** {{justification}}

#### Segregation of duties review

**Table:**

**Columns:**

- Check
- Result

**Rows:**

**0:** User can create and post purchase invoices

**0:** User can maintain vendor bank accounts

**0:** User can post to the G/L and approve payments

**0:** Conflicts documented and accepted by owner

#### Approvals

**Signatures:**

- Requester
- Line manager
- Process owner
- BC administrator

**Notes:** Starting point only; adapt to your own policy. Permission set names are examples, so check the exact names and any custom sets in your environment. Review users and access regularly and remove accounts of leavers promptly. This is not legal or audit advice.

## Content

**Intro:** Controlled access to Business Central is a basic audit expectation. This form captures who needs access, what license and permission sets are requested, the business reason, and the approvals, so a BC administrator can set up the user without guessing.

**Sections:**

#### How to use it

**Body:** Fill in the requester details, license and role center, then list the permission sets. Describe the business justification in plain words. Use the segregation of duties table to record whether the access creates a conflict, for example one person who can both enter purchase invoices and maintain vendor bank details. Export to PDF, collect signatures and file it with your change records.

#### What the administrator does with it

**Body:** In Business Central the administrator creates the user from Microsoft 365 or Entra ID, assigns a license in the admin center, then opens Users and adds the permission sets. Companies are controlled through user permissions per company. Keep the request ID in the permission set assignment note so an auditor can follow the trail from form to setting.

**Bullets:**

- Assign a license first in the Microsoft 365 admin center
- Use user groups to bundle common permission sets
- Assign by role, not by individual preference
- Review SUPER and SECURITY sets with extra care

#### Good practice

**Body:** Grant the least access needed. Prefer a small set of well-named job roles over many one-off combinations, and use temporary access with an end date for cover or projects. Review user lists each quarter with process owners, and keep evidence of the review. Sandboxes deserve rules too, especially if they contain production copies.

#### Common mistakes

**Body:** Copying another employee's permissions wholesale, leaving SUPER on a former consultant, giving shared accounts to avoid license cost, and never removing leavers. Another is skipping the review of custom permission sets added by extensions, which can open surprising access.

**Cta:** If you want a read-only report of who holds which permission sets and which users have conflicting rights, we can build it from your BC security tables.

**Faq:**

#### Which permission sets should a new user get?

**Answer:** Start from your role definitions. Many companies use D365 BASIC plus functional sets for the job, such as purchasing or sales. Avoid SUPER unless the person is an administrator.

#### Is this form audit compliant?

**Answer:** It supports an access control process but compliance depends on how you operate it. Keep approvals, review the access list on a schedule and document exceptions.

#### Can I use it for sandboxes?

**Answer:** Yes. Choose the sandbox environment. Treat sandboxes that hold copies of production data with the same care as production.

#### How should I handle leavers?

**Answer:** Use the Remove access request type, disable the user in Business Central and revoke the license on the day of departure. Keep the form as evidence.

## Search terms

business central user access request form, business central user setup template, user access request form erp, business central permission set request, segregation of duties request form, business central onboarding checklist user

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json