What does read-only mean?
Read-only is a form of access where software can only read the information in a database and cannot change it in any way. READERP connects this way to the common ERP and finance platforms on the market, led by Netsis and Logo, the ERP systems widely used in Türkiye. It never writes a single row to your ERP: it does not issue invoices, open account cards or create stock movements, and it does not change or delete any existing record.
That is why your accounting team's routine, your ERP dealer's support and your existing reports all carry on as they are. READERP does not replace your ERP; it sits alongside it as a reading layer.
Why does it matter?
| Concern | With read-only access |
|---|---|
| Could the reporting tool change a record by mistake? | No, it has no write permission |
| Will ERP updates cause problems? | No settings or structural changes are made in the ERP |
| Is the accounting close affected? | No, records stay exactly as they are |
| Will dealer support be affected? | No, the ERP is not touched |
How is security ensured?
Read-only permission is a safeguard on its own, but READERP does not stop there. The layers work like this:
- Database permission: The connection uses a separate user that has read permission only.
- Query gate: The agent running on your company's server checks every incoming query against its own rules. It allows only read queries and sets row and time limits.
- Signed tasks: The agent runs only tasks signed by the platform. Requests from any other source are refused; the signature also covers the target server and database.
- Agent identity: The agent identifies itself to the platform with its own key. When the key is revoked, the installation stops immediately.
- Local log: Every query that runs is also written to a local log on your own server, so you can see exactly what was read.
Same-day setup
The read-only approach also speeds up setup. Because there is no need to create tables, add triggers or upgrade versions in the ERP, setup is finished the same day once your IT team's preparation is complete. Fiscal-period databases are mapped and the ready-made sections work from day one.
Checklist for your IT team
- The server running the ERP database, and access details
- A database user with read-only permission
- The server or computer where the agent will run
- A firewall rule for the outbound connection
- Which fiscal-period databases to include in reporting
KVKK and access rights
Customer/supplier accounts and payroll include personal data. Who sees which report is defined by role; the Payroll section shows totals and never individual salaries. We fully meet the requirements of KVKK (Türkiye's Personal Data Protection Law) and charge nothing extra for it. Our overall approach is on the our KVKK approach page.
Frequently asked questions
Does read-only access slow down the ERP?
Queries have row and time limits, and heavy queries can be scheduled to run outside peak hours.
Can we see which queries are run?
Yes. Every query that runs is written to the local log on your own server, and your IT team can review it at any time.
For the full service, go back to the ERP reporting page, or get in touch to plan your setup.