TexaCore is a general ERP for business owners and accountants, bringing accounting, inventory, and sales together in a free-forever desktop edition that works offline. Check the current subscription catalogue for cloud pricing, trial terms, and current limits.
· TexaCore
The short answer
A company stays in control when three things work together: permissions that decide what each person can see and do, tasks that have an owner, a due date and a department, and a trail that shows who changed what. Where people share one login and tasks live in chat groups, none of the three exists. TexaCore provides a permission matrix with custom roles that limit users to branches, warehouses and cash accounts, approval rules that the server enforces, the option to hide cost and profit, tasks assigned by owner and department in list and calendar views, task analytics and an activity trail. The analytics group tasks by owner and category; a per-department scorecard is not among the published capabilities.
Where control slips
Control usually slips in the same seven places:
- Everyone shares one login. Nobody can say who changed a figure or approved a discount.
- Everyone sees everything. The cashier sees cost and profit, the storekeeper sees salaries, and every user sees every branch.
- The person who asks also approves. A discount, a write-off or an advance is signed off by the one who wanted it.
- Tasks live in chat groups. There is no owner, no due date and no way to see what is overdue except by scrolling.
- Nobody can tell which department is behind. A manager asks by phone and gets an opinion instead of a count.
- Sensitive steps are open. Payroll approval, reopening a period or changing a role can be done by whoever happens to have the screen open.
- After a mistake there is no trail. Reconstructing what happened means asking around.
What it costs the business
The effects are qualitative; how large they are depends on your size and on how much you can afford to rest on habit.
- Sensitive figures leak. Margins, costs and salaries travel through informal channels.
- Mistakes cannot be traced, so they cannot be fixed at the cause or attributed fairly.
- Work waits unnoticed. A task without an owner and a date is simply not done, and nobody knows until a customer asks.
- Workloads are uneven. Some people are overloaded and others idle, and the manager cannot see which.
- Approvals become a formality, because nobody else is ever asked.
- Growth makes it worse. Every new branch, warehouse or hire multiplies the number of people who can touch everything.
What good control looks like
Three principles are enough to start. Give each person the least access that lets them do the job. Split sensitive actions between two people, so that whoever asks does not also approve. Keep a record of who did what, without relying on anyone’s memory. Public security catalogues state the same ideas: NIST SP 800-53 lists least privilege and separation of duties among its access-control measures, and the OWASP Application Security Verification Standard lists access-control requirements for web applications.
For tasks the same logic applies in a lighter form: every task has one owner, a due date and a place, so that “overdue” is a list and not an argument.
How TexaCore solves it
Each row is a published capability of branches and companies, the CRM, HR and payroll or the sales approval rules. All of them are available today.
| The problem | What TexaCore does | Status |
|---|---|---|
| Everyone shares one login | A per-document activity timeline (created, confirmed, posted, edited, printed) shows who performed an action, and an audit log records changes to permissions and roles. | Available today |
| Everyone sees everything | A permission matrix and custom roles (such as branch manager and cashier) limit each user to specific branches, warehouses and cash accounts, while owners and admins keep full control. Document visibility can be scoped to the owner, team or company. | Available today |
| Cost and profit are visible to everybody | Hide profit and cost figures from users who do not have the permission. | Available today |
| The person who asks also approves | Approval rules for sales and purchase documents: always, above an amount or discount, or when the customer exceeds the credit limit. The server enforces them, and approvers cannot approve their own document (the owner excepted). A damage write-off goes through approval too. | Available today |
| Sensitive steps are open | Payroll periods are approved, paid and reopened under a dedicated permission with total checks; the owner can approve from a Telegram card, and employees confirm receipt of their payslip. | Available today |
| Tasks live in chat groups | Assign tasks by owner and department with priority, category and due date, and use list and calendar views to see what is overdue and what needs follow-up. A comment with a follow-up date creates a linked task. | Available today |
| Nobody can tell who is behind | Task analytics compare completed, open and overdue tasks and their distribution by owner and category, from your company’s own task records. A follow-up board shows overdue tasks and opportunities without an owner. | Available today |
| Staff who work from their phones | The Telegram staff bot shows each person only the buttons their permissions allow; a manager can reorder, hide or rename buttons, which does not change permissions. The company’s own bot must be configured, the interface is in Arabic and an internet connection is required. | Available today |
| People, departments and requests | Departments, positions and a vacancy plan on the employee file; employee requests (leave exception, advance, resignation, certificates) are routed from HR to accounting to a decision. | Available today |
Know the limits. Task analytics group by owner and by category: a per-department performance scorecard is not among the published capabilities, so use department assignment and the owner view together. Tasks belong to the customer workflow in the CRM and are not a separate project-management tool. A due date does not create an automatic reminder. Financial reports are per company, with no per-branch reports.
How to start
- List your roles, not your people: owner, branch manager, cashier, storekeeper, accountant, salesperson, and what each should be able to see.
- Create the custom roles from that list and give each user their branches, warehouses and cash accounts. Keep owner and admin rights for as few people as possible.
- Decide the approval rules: which discounts, credit limits and write-offs need a second person.
- Move recurring follow-ups out of chat groups into tasks with one owner, a department and a due date.
- Review once a week: overdue tasks by owner, then the activity timeline of any document that looks wrong.
Cloud plans start with a 30-day free trial. The number of companies and branches is a limit of each plan and is shown on the pricing page.
About this article
Published by TexaCore. It explains general ideas in plain terms; security, labour and statutory rules are not covered, so confirm them with a qualified adviser. Statements about TexaCore describe the modules’ published pages on the date above, and each feature row carries its status. The outside sources used are listed under Sources.
Related reading
FAQ
- Can I limit a user to one branch and one cash account?
- Yes. A permission matrix and custom roles, such as branch manager and cashier, limit each user to specific branches, warehouses and cash accounts. Owners and admins keep full control.
- Can I hide cost and profit from some users?
- Yes. Profit and cost figures are hidden from users who do not have the permission.
- Can the person who creates a document approve it?
- Not under an approval rule. The server enforces the rule, and approvers cannot approve their own document, except the owner.
- How do I see who is behind on tasks?
- Give each task an owner, a department and a due date. List and calendar views show what is overdue, and task analytics compare completed, open and overdue tasks by owner and category. A per-department scorecard is not available.
- Does TexaCore send automatic reminders for tasks?
- No. A due date does not create an automatic reminder. The follow-up board highlights overdue tasks and unassigned opportunities for your team to review.
- Can staff work from Telegram without seeing everything?
- Yes, once the company’s own bot is configured and the user’s account is linked: the bot shows each person only the buttons their permissions allow. The bot interface is in Arabic and needs an internet connection.
Sources
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations — NISTAccess-control measures including least privilege and separation of duties.
- OWASP Application Security Verification Standard (ASVS) — OWASP FoundationA public catalogue of access-control and other security requirements for web applications.