Frequently asked questions
Everything you'd ask before moving your operations across.
Straight answers on what is included, who can see what, how integrations are billed to your own accounts, and how your data stays separated.
Getting started
Setting up a workspace and bringing your organisation onto the platform.
Eduthropy is operations software for nonprofits, social enterprises and small businesses. It joins the parts of running an organisation that usually live in separate spreadsheets, funding and income, budgets and spend, delivery plans, people and payroll, and the paperwork around all of it, into one workspace with a shared audit trail.
Most organisations create a workspace, add their team and record their first budget in an afternoon. You choose your organisation type during onboarding, which decides the terminology and the modules you see, so you are not walked through anything that does not apply to you.
No. Start with one area, usually finance or delivery, and add the rest as you go. Budgets and transactions can be imported later from Xero, QuickBooks or a spreadsheet with column mapping and a preview before anything is written.
What's included
The modules that make up the platform and how they connect.
Portfolios, programmes and projects sit above workplans, activities and tasks, so a funded piece of work traces down to the person doing it this week. Alongside that you get a RAIDD log for risks, issues, assumptions, dependencies and decisions, and KPIs with targets and dated reach entries.
Budgets with categories and departments, transactions posted against budget lines, expense requests with approval and retirement, payroll runs with payslips, invoices and products for earned income, and donations and grants on the fundraising side. Summary figures convert into your base currency automatically.
A team directory with line managers, performance and appraisals, document storage, holiday and time off, and scenario-based simulations that staff can be assigned and that feed evidence back into appraisals.
Roles & permissions
Who sees what, and who has to approve it.
Owner, admin, manager and member. The owner is fixed and always sees everything; the other three are defined by the owner, module by module.
Per module and per settings tab you can set no access, read only, edit, edit with approval, delete with approval, or full access. Approval can be routed to the owner or to the person's line manager, so day-to-day sign-off can be delegated without handing over the keys.
Yes. Individual overrides let an owner pick a staff member and change specific modules for them, while everything else continues to follow their role.
Question we haven't answered here?
Open a workspace and ask us from inside it, we help with the first import and your permission setup.