# Epicor Kinetic User Access Request Form Template

> Source: https://netray.co/tools/epicor-kinetic-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 for requesting, changing or removing Epicor user access, with security group, company and approval fields.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor administrator
- IT manager
- Internal auditor

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Request type

**Key:** request_type

**Type:** select

**Options:**

- New user
- Change access
- Disable user
- Temporary access

**Default:** New user

#### Employee name

**Key:** user_name

**Type:** text

**Default:** Priya Nair

#### Epicor user ID

**Key:** user_id

**Type:** text

**Default:** PNAIR

#### Department

**Key:** department

**Type:** text

**Default:** Purchasing

#### Manager

**Key:** manager

**Type:** text

**Default:** R. Chen

#### Epicor company or site

**Key:** epicor_company

**Type:** text

**Default:** Main plant

#### Security groups requested

**Key:** groups

**Type:** textarea

**Default:** Buyer group, Inventory inquiry group

#### Menu or function access needed

**Key:** menus

**Type:** textarea

**Default:** Purchase Order Entry, Supplier Entry (view), Part Tracker

#### End date (temporary access)

**Key:** end_date

**Type:** date

#### Business reason

**Key:** reason

**Type:** textarea

**Default:** New buyer joining the purchasing team.

**Blocks:**

#### Epicor User Access Request

**Body:** Company: {{company}}
Request type: {{request_type}}
Employee: {{user_name}}
Epicor user ID: {{user_id}}
Department: {{department}}
Manager: {{manager}}
Company or site: {{epicor_company}}

#### Access requested

**Body:** Security groups:
{{groups}}

Menus and functions:
{{menus}}

Temporary access end date: {{end_date}}

#### Business reason

**Body:** {{reason}}

#### Segregation of duties check

**Table:**

**Columns:**

- Question
- Yes/No
- Comment

**Rows:**

**0:** Can the user both create and approve purchase orders?

**0:** Can the user both enter and post supplier invoices and maintain supplier bank data?

**0:** Can the user adjust inventory and also approve counts?

**0:** Does the user need access to financial settings or user maintenance?

#### Approvals

**Signatures:**

- Requesting manager
- Process owner
- Epicor administrator
- Date access granted

**Notes:** Align the segregation of duties questions with your own audit requirements. This is a starting point for your access control procedure.

## Content

**Intro:** Access requests sent by email lose detail and approvals. A standard form tells the administrator exactly which security groups to assign, who approved it and when temporary access must end.

**Sections:**

#### How to use the form

**Body:** The requesting manager fills in the identity and access fields. The process owner confirms the roles are appropriate and the administrator grants them in the system, then records the date. Export the completed form as PDF and keep it with your access review records. For leavers, use the Disable user type and complete it the same day.

**Bullets:**

- Request security groups, not individual menus, where you can
- Set an end date for contractors
- Keep the signed copy for audits

#### Security groups and menus

**Body:** Epicor controls access through security groups combined with menu and function permissions, and a user can belong to more than one group. Because permissions accumulate, a user who moves departments can end up with old and new rights together. The change access request type exists to make administrators remove what is no longer needed rather than only adding.

#### Segregation of duties

**Body:** The checks table flags the combinations that auditors ask about: raising and approving the same purchase, entering invoices and changing supplier bank details, adjusting stock and approving counts. If any answer is yes, record the compensating control, such as a review report. Keep the questions to those that matter in your business so the form stays quick.

#### Common mistakes

**Body:** Copying another user's access is the most common shortcut and the most common source of excess rights. Another is forgetting to disable accounts of leavers and contractors. Review all users at least twice a year against HR records.

**Bullets:**

- Cloning access from a colleague without review
- No end date on contractor accounts
- Shared logins for shop floor terminals

**Cta:** If you need to review who can do what across hundreds of users, we can help build a private assistant that analyses your exported security data and flags risky combinations.

**Faq:**

#### Should the form list security groups or menus?

**Answer:** Prefer security groups. They are easier to review and keep consistent. Use the menu field only for exceptions, and record why the exception exists so the next review can challenge it.

#### How long should we keep completed forms?

**Answer:** Follow your audit and record retention policy. Many companies keep them for the audit cycle plus a year or more. The point is that you can show who approved each person's access.

#### Is this suitable for SOX or similar controls?

**Answer:** It supports the evidence trail, but your control design must come from your compliance team. Use the form as an input and align approvers and checks with your documented controls.

#### Can contractors use the same form?

**Answer:** Yes, choose Temporary access and set the end date. Add the sponsoring employee as manager so someone is accountable for removal.

## Search terms

epicor user access request form, epicor new user setup template, epicor security group request, erp access request form, epicor user onboarding form, epicor segregation of duties form

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