Which principles should decide who sees SAP figures?
Three principles cover most decisions: give the least access the job needs, follow your organization structure, and review access regularly. Write them down so every request is judged the same way.
- Least access. Start each person with nothing and add what their job needs. A sales manager for one region needs that region's sales and receivables, not payroll costs for the whole group.
- Follow the organization structure. Tie access to units that already exist in SAP, such as company codes and plants. When the structure changes, you know exactly which access to change.
- Review regularly. People move, projects end and consultants leave. Access that was right last year may be wrong today.
Keep seeing separate from doing. Many people need to view figures. Far fewer need to build dashboards, share them or manage users.
Which dimensions should you restrict by?
Restrict first by subject, then by organizational unit. You will often combine them, for example finance figures for two company codes, or sales figures for one sales organization only.
| Dimension | What it means | Example restriction |
|---|---|---|
| Business area | The subject, such as sales, purchasing or finance | Buyers see purchasing figures but not margins by customer |
| Company code | A legal entity that keeps its own books | A country manager sees only the company in their country |
| Sales organization | The unit responsible for selling, with its own sales terms | A regional sales head sees only their region's orders and billing |
| Plant | A factory, warehouse or site where goods are made or stored | A plant manager sees production and stock for one site |
| Purchasing organization | The unit that buys from suppliers and negotiates terms | A purchasing lead sees spend for the units they manage |
SAP also uses the term business area for an organizational unit in financial accounting. In this guide it simply means the subject of a report.
Should you use roles or individual grants?
Use roles for what people can do and groups for people who need the same access. Keep individual grants for exceptions, and give them an end date.
- Roles bundle permissions, such as viewing, building, sharing and managing users. A few standard roles cover most people.
- Groups collect people with the same needs, such as plant managers or regional sales heads. One group membership is easier to check than many separate grants.
- Individual grants cover genuine exceptions. Record why each one exists.
- Shares with end dates suit temporary needs: audit work at year-end, a consultant on a project or cover during leave. Set the end date when you share, not later.
Common mistakes to avoid:
- Making many people admins because it is quicker than setting up roles.
- Copying a colleague's access for a new joiner, including access the colleague should not have.
- Sending exported files, which takes the figures outside any access control.
- Forgetting that a person who changes jobs keeps their old access until someone removes it.
How do you run an access review?
Export who can open what, have each manager confirm their people's access, and remove anything nobody can justify. Put the review in the calendar like month-end, for example every quarter and after any reorganization.
- Export the current list of who can open which dashboards, reports and plans.
- Send each manager the lines for their team.
- Confirm or remove each line. If nobody can say why access exists, remove it.
- Check joiners, movers and leavers since the last review.
- Find shares with no end date, then add one or remove the share.
- Check the activity log for admin changes and unusual sign-in patterns.
- Record the date and outcome of the review for your auditors.
How does LendraBI control who sees which figures?
LendraBI is private by default: people see what they made or what was shared with them, and admins see everything in their organization. From there you add access by role, group and access profile.
- Roles with 21 permissions. Use the built-in Admin, Editor and Viewer roles, or create custom roles.
- Groups for people who need the same access.
- Access profiles limit people to business areas such as sales, purchasing and finance, and to the company codes, sales organizations, plants and purchasing organizations you choose.
- Your SAP authorizations, if you want them. Optionally, each person signs in with their own SAP user so their SAP authorizations apply.
- Share end dates so temporary access ends on time, with a notice three days before a share ends.
- Access requests. Someone who needs a dashboard can ask for access, and the owner decides.
- A searchable activity log of every sign-in, share and admin change.
- An Excel export of who can open what, ready for your access review.
- Sign-in protection with authenticator-app two-step sign-in, session control and lockout after failed attempts. Passwords, tokens and connection details are encrypted at rest.
Scheduled email reports go only to people in your organization, and fewer Excel exports from SAP means fewer copies of figures outside these controls. To set up alerts and reports with the same care, see KPI alerts and scheduled reports, and for the wider picture read about ways to report on SAP data. To walk through roles and access profiles for your own structure, book a demo.
Questions
Can LendraBI use our existing SAP authorizations?
Yes, optionally. Each person can sign in with their own SAP user, so their SAP authorizations apply.
Can I limit someone to one company code or plant?
Yes. Access profiles limit people to business areas and to the company codes, sales organizations, plants and purchasing organizations you choose.
How do I see who has access to what?
Export the Excel list of who can open what, and search the activity log for sign-ins, shares and admin changes.
Can I give someone temporary access?
Yes. Set an end date when you share, which suits temporary needs such as year-end audit work or a project.
Does LendraBI support two-step sign-in?
Yes. It supports two-step sign-in with an authenticator app, along with session control and lockout after failed attempts.