EN
Bookkeeping

How to Set Up User Permissions? Training on Permission Matrices in Accounting Software, Segregation of Duties and Fraud Prevention

How do you set up user permissions? Permission matrix, least privilege principle, segregation of duties, branch restrictions, IP restrictions and activity auditing: an 8-lesson guide with examples.

Contents 14 sections
  1. What will you be able to do by the end of this training?
  2. Lesson 1: Why are user permissions necessary?
  3. Lesson 2: What is the principle of least privilege?
  4. Lesson 3: How are roles defined?
  5. Lesson 4: How do you prepare a permission matrix?
  6. Lesson 5: How do you apply segregation of duties?
  7. Lesson 6: How do you set branch, warehouse and IP limits?
  8. Lesson 7: How do you audit activity logs?
  9. Lesson 8: How do you manage permissions across the employee lifecycle and set up a monthly routine?
  10. What are the most common mistakes in setting permissions?
  11. How does NetKasam make permission management easier?
  12. Mini quiz: Test what you have learned
  13. Conclusion: Write a permission matrix this week
  14. Frequently Asked Questions About User Permissions

Can your warehouse worker see cost reports? Can your sales representative cancel invoices? Is the person who does the accounting also the person who approves payments? In small businesses, these questions often go unasked because "everyone trusts each other." But when permissions are unlimited, a wrong click, a malicious action or a departed employee's account left open turns into lost money and data. The solution is not distrust but user permissions: everyone has only as much access as they need to do their job.

This article is not an overview but an 8-lesson hands-on training. It answers the question how do you set up user permissions using a sample business with 12 people; we will work through the principle of least privilege, roles and the permission matrix, segregation of duties, branch and IP restrictions, auditing activity logs and the employee onboarding and offboarding process in order. At the end there is a mini quiz and a monthly audit routine. For the general framework of internal control, see the article internal control system, and for signs of errors and fraud, see how to detect accounting errors and fraud.

What will you be able to do by the end of this training?

In short: You will group your employees into roles, write a permission matrix, segregate duties, set branch and IP limits, audit activity logs and update permissions during onboarding, role changes and departures.

Training mapThe six steps of user permissions
  1. 01
    RoleGroup employees into roles by their duties.
  2. 02
    MatrixWrite down what each role can do in each module.
  3. 03
    SegregationSeparate the people who initiate, approve and pay.
  4. 04
    LimitsSet branch, warehouse and IP limits.
  5. 05
    MonitoringReview activity logs regularly.
  6. 06
    LifecycleUpdate permissions at onboarding, role changes and departure.

The training's 8 lessons: (1) why permissions, (2) the principle of least privilege, (3) defining roles, (4) the permission matrix, (5) segregation of duties, (6) branch and IP limits, (7) activity log auditing, (8) the employee lifecycle and monthly routine.

Lesson 1: Why are user permissions necessary?

In short: Permissions limit who can see and do what in a system. By preventing errors, malicious intent and data leaks, they protect both money and customer data.

Unauthorized useExampleWith limited permissions
Wrong actionA warehouse worker accidentally changes the price listThe warehouse worker cannot see or change prices
Malicious intentA sales representative gives their own customer a hidden discountOnly the manager has discount permission
Information leakAn employee copies the customer list and costsNo access to cost and customer list reports
Account left openA departed employee's account stays open for monthsThe account is closed on the day of departure

Permissions are not a declaration of distrust; they also protect trustworthy employees against wrong clicks. For NetKasam's general approach to protecting customer and company data, see the data security page.

Lesson 2: What is the principle of least privilege?

In short: The principle of least privilege means giving each user the narrowest permissions they need to do their job. Permissions are added later when needed; granting broad permissions up front and narrowing them later is much harder.

  1. Define the job: What will this person do (issue invoices, enter inventory, prepare orders)?
  2. Identify the required screens: Which modules must they access for this job?
  3. View only, or process? For most employees, viewing is enough.
  4. Separate sensitive permissions: Consider cancellation, deletion, discount, payment and report permissions separately.
  5. Grant temporary permissions: Permissions granted to cover a leave or for the duration of a project should have an end date.

Lesson 3: How are roles defined?

In short: A role is a shared set of permissions for people who do similar work. Instead of thinking about each employee individually, define 4-6 roles and assign employees to a role; managing permissions becomes easier and stays consistent.

Our sample business has 12 people (the figures were chosen only to illustrate the method):

ChartRole distribution of the sample business's 12 users
  • Sales₺433.3%
  • Warehouse₺325%
  • Customer service and shipping₺216.7%
  • Accounting₺216.7%
  • Manager₺18.3%

Prepared with sample values.

RoleMain dutyAreas not needed
SalesEntering orders, viewing customer accountsCost, bank, cash, reports
WarehousePicking orders, entering inventory movementsPrices, account balances, bank
Customer service and shippingOrder status, shipment trackingPrices, cost, bank
AccountingInvoices, collections, expenses, customer and supplier accountsInventory count adjustments, payment approval
ManagerApprovals, reports, permission managementDaily warehouse operations

Lesson 4: How do you prepare a permission matrix?

In short: A permission matrix is a table with modules in the rows and roles in the columns, and each cell says "none," "view," "process" or "approve." Once the matrix is written down, everyone knows who can do what, and inconsistencies in the system become visible.

ModuleSalesWarehouseCustomer serviceAccountingManager
OrderTransactionProcess (preparation)ViewViewApprove
Inventory movementsViewTransactionViewViewApprove
Prices and discountsViewNoneNoneViewApprove
InvoicingNoneNoneNoneTransactionView
Customer and supplier accounts and collectionsViewNoneNoneTransactionApprove
Cash and bankNoneNoneNoneTransactionApprove
Cost and profit reportsNoneNoneNoneViewView
Users and permissionsNoneNoneNoneNoneApprove
ChartNumber of users with process or approve permission per module in the sample matrix: sensitive modules are kept narrow
  1. Orders8 people
  2. Inventory movements4 people
  3. Cash and bank3 people
  4. Customer and supplier accounts and collections3 people
  5. Invoices2 people
  6. User and permission management1 person

Prepared with sample values. The numbers are derived from the role distribution and the matrix above; for example, cash and bank: 2 accounting + 1 manager.

In NetKasam, you can define different permissions for your employees and manage permission limits down to the finest detail (can I define different permissions). You can also prevent users from accessing report pages (can I restrict them from running reports). Mirror this matrix exactly in the system and update it whenever it changes.

Recommended readingHow Do You Calculate a Sales Bonus?

Lesson 5: How do you apply segregation of duties?

In short: Segregation of duties means that initiating, approving and recording a transaction involving money or inventory are done by different people. If the same person does all of them, errors or fraud go unnoticed.

TransactionInitiatorApprover / checkerRecorded by
Supplier paymentPurchasing / managerManagerAccounting
Inventory count discrepancy adjustmentWarehouseManagerAccounting
Discount to a customerSalesManagerAccounting
Returns and cancellationsCustomer serviceManagerAccounting
Cash countRegister supervisorManagerAccounting

In a small business with few people, you cannot make every separation; in that case, manager approval and a weekly review are compensating controls. For the cash side, see the cash closing guide; for the bank side, bank reconciliation; and for inventory discrepancies, inventory count. Where these checks are done regularly, segregation of duties works more effectively.

Lesson 6: How do you set branch, warehouse and IP limits?

In short: In a business with multiple branches, link each user only to their own branch and warehouse; by limiting access to specific IP addresses, ensure the system is used only from the workplace.

  1. Branch and warehouse link: Assign each user their own branch or warehouse so they don't see the other branch's inventory and sales.
  2. Wholesale and retail separation: Define the branch's sales terms and block sales outside them.
  3. IP restriction: For sensitive roles (accounting, manager), restrict access to the office IP address only.
  4. Mobile access: Question whether anyone other than managers needs external access.

In NetKasam, you can define separate users and separate permissions for each of your stores or warehouses (separate permissions for my branch staff), and with the IP restriction feature, allow users to access the system only from specific IP addresses. For branch-based reporting, see the branch and warehouse management page.

Lesson 7: How do you audit activity logs?

In short: Granting permissions is not enough; you need to monitor how they are used. Check the activity logs in the system weekly and monthly; cancellations, deletions, discounts, price changes and after-hours activity are the warning signs to look at first.

Audit questionWhy?Sign
Which user makes the most cancellations?Fraud or lack of trainingSeveral times as many cancellations as others
Who made price and discount changes?Unauthorized discountPrice changes by the sales role
Is there activity outside working hours and on weekends?Unauthorized accessInvoices and collections late at night
Who has deleted transactions or ones cancelled with a reversing entry?MonitoringThe same user recurring
Is the same user logging in from multiple devices or IPs?Account sharingSeveral people under one username

In NetKasam, every action users take is logged and cannot be deleted; this lets you track users' full activity log (can I see the actions users take). When you cancel an expense receipt, all movements of the transaction are updated with a reversing entry, so the history also stays traceable. Account sharing is the biggest traceability gap: give each employee their own user account.

Lesson 8: How do you manage permissions across the employee lifecycle and set up a monthly routine?

In short: Permissions are updated at the moments of onboarding, role change and departure. A monthly review catches forgotten accounts and permissions that exceed a person's role.

MomentTo doDuration
OnboardingCreate the user, grant the role's permissions, short training on the first dayFirst day
Role changeRemove the old role's permissions and grant the new onesSame day
LeaveFor long leaves, deactivate the account or reduce it to narrow permissionsAt the start of the leave
DepartureClose the account and end password and device accessDay of departure
Monthly auditCompare active users, their roles and permissions against the matrixMonth-end
FormulaFour indicators for the monthly permission audit
  1. Share with permissions outside their role = Users with permissions outside their role ÷ Total users
  2. Share of inactive but open accounts = Accounts of departed or on-leave staff that are still active ÷ Total accounts
  3. Number of shared accounts = Usernames used by more than one person
  4. Sensitive module access = Number of users accessing cash, bank and cost reports

The target for the four indicators is zero; for the numeric one, the target is the minimum.

Takeaways from the exampleFour numbers from the sample monthly audit
  • 3 / 12users with permissions outside their role (25%)
  • 2departed employees whose accounts are still open
  • 1account used by two people
  • 3people with cash and bank access

If the sample audit finds that 3 of 12 users have permissions outside their role, the share is 25%; two departed employees' accounts are open, and one account is shared by two people. All three are corrected, and the same numbers are worked out again the following month.

Recommended readingWhat Is Online Accounting and How Does It Work? Differences From Desktop Software, Working With an Accountant and a Migration Checklist

What are the most common mistakes in setting permissions?

  1. Giving everyone admin permissions. It gets you started fast, but the risk is unlimited.
  2. Sharing accounts. Nobody knows who performed an action.
  3. Leaving a departed employee's account open. The former employee can still reach the data.
  4. Not removing old permissions after a role change. Permissions pile up.
  5. Not writing a matrix. Who can do what is based on guesswork.
  6. Ignoring segregation of duties. The same person initiates, approves and records.
  7. Never looking at activity logs. The use of permissions goes unaudited.

How does NetKasam make permission management easier?

  • You add users yourself. You define new users from the general settings page without needing technical support (adding a new user).
  • Detailed permissions. You manage each user's permission limits down to the finest detail and define their working area (user and employee management).
  • Branch- and warehouse-based users. You define separate users and permissions for each branch and warehouse.
  • IP restriction. You allow users to access the system only from specific IP addresses.
  • Undeletable activity log. Every action users take is logged; you can review the log whenever you like.
  • Report access restriction. You block access to report pages on a per-user basis (reports).
  • Free bookkeeping, unlimited users. e-Invoice, customer and supplier accounts, inventory, cash, bank and expense management are free in every plan and there is no user limit; for details, see the pricing page.

Mini quiz: Test what you have learned

In short: Answer the 5 questions below, then compare with the answer key. 4 or 5 correct shows you have completed the training.

  1. What is the principle of least privilege?
  2. If 4 of 15 users have permissions outside their role, what is the "share with permissions outside their role"?
  3. If the same person both initiates and approves a supplier payment, which rule is broken?
  4. Why is a departed employee's account closed the same day?
  5. How does account sharing weaken auditing?

Answer key:

  1. It means giving each user the narrowest permissions they need to do their job.
  2. 4 ÷ 15 = %26,7.
  3. Segregation of duties; the initiator, approver and recorder should be different people.
  4. An open account lets the former employee access data and transactions; the risk starts on the day they leave.
  5. It becomes impossible to determine who performed an action; the logs lose their meaning.

Frequently Asked Questions About User Permissions

How do you set up user permissions?

Employees are grouped into roles by their duties, what each role can do in each module is written in a permission matrix, duties are segregated, branch and IP limits are set, and activity logs are audited regularly.

What is the principle of least privilege?

It means giving each user only the permissions they need to do their job and nothing more. Permissions are added when needed.

What is a permission matrix?

It is a table with modules in the rows and roles in the columns, where each cell states the permission level (none, view, process, approve).

Why is segregation of duties important?

If initiating, approving and recording a transaction are done by different people, errors and fraud are noticed more easily; concentrating them in one person creates risk.

When should a departing employee's account be closed?

On the day they leave. Leaving the account open keeps the former employee's access to company data.

Can I give employees different permissions in NetKasam?

Yes. You can define separate permissions for each employee and ensure that each user works only within their own area. You can manage permission limits down to the finest detail.

Can I see users' actions in NetKasam?

Yes. Every action users take is logged in the system and cannot be deleted; you can track the full activity log in detail.

Does NetKasam have IP restrictions?

Yes. By allowing users to access the system only from specific IP addresses, you can increase the security of company data.

Conclusion: Write a permission matrix this week

There is no need to turn permissions into a project: this week, group your employees into five or six roles, write a permission matrix and compare the actual permissions in the system against it. Close permissions held outside a role, accounts of departed staff that are still open and shared accounts. Repeat the same check at the end of the month; the next surprise will be a small one.

Bookkeeping Is Now Completely Free

Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.

Start FreeCustomer and Supplier Account Tracking

Read similar articles

19 free tools

Commission, shipping, VAT and profit calculations in your browser, no sign-up needed.

All tools