# Bring every unit onto one app, with the controls IT asks for > Projects, time, people and cost for the whole organisation in one place. Your directory decides who joins and leaves, permission sets decide who sees what, and every change to access is on record. - [Book a demo](https://akollo.com/en/demo) - [Read the docs](https://docs.akollo.com/en) ## How a large organisation rolls out Akollo Start with one unit and add the next on the same installation. The structure, access and records grow with you. 1. **Map the organisation as it really is** (Units) — Companies, regions, branches, divisions, departments and teams as one tree, viewable on any date. A move between units is a transfer, so history stays correct. 2. **Let your directory decide who joins and leaves** (Sign-in and directory) — Connect your sign-in provider and directory, for example through SCIM. Group mappings give roles and units, and each change is previewed and approved by a second administrator. 3. **Give each person exactly the access they need** (Roles & permissions) — Permission sets bundle the actions each module offers. Field policies hide or mask sensitive fields, and Explain access shows where any permission comes from. 4. **See every programme across the units** (Projects and portfolios) — Group projects into portfolios, follow them on one timeline and read the status updates leads publish, with cost by department alongside. 5. **Show it all at audit time** (Governance) — Privilege and configuration changes go to the audit log. Access review campaigns check who still needs what, and retention rules decide how long data is kept. ## The views administrators and leaders open The same records serve the programme lead, the unit head and the auditor, each within the access they hold. ### Organisation admin Counters for units, active members, delegations and open access reviews, people per unit and everything waiting for approval. - Members without a unit - Joiners and leavers waiting - Review items due ### Portfolio timeline Projects, epics and items from many teams on one time axis, with dependencies, milestones, sprints and a line for today. - Critical path - Milestones across projects - Portfolios nested three levels deep ### Roles & permissions Permission sets, who holds them, field policies and the changes waiting for a second administrator, in one place. - Strictest field policy wins - Explain access per person - Admin rights need a second approver ### Access reviews Campaigns for a unit, a role, everyone with admin rights, contractors or service accounts, with due date and progress. - Nobody reviews their own access - Keep or revoke with a reason - Results as CSV or Excel ## What you can show the board and the auditor No figures pulled together by hand from five tools. These come from the records Akollo already keeps. - **Cost and margin by department** — Cost, expenses, revenue and margin month by month for each department, from approved hours and rates. (Budgets & profitability) - **Access nobody has confirmed** — Review items still open per campaign, and what happens to them at the due date, so stale access does not linger. (Admin › Access reviews) - **Joiners, movers and leavers** — Lifecycle cases from your directory by state: waiting for approval, running, failed, set aside or completed. (Admin › Joiners and leavers) - **Usage per day** — AI, API calls, storage and exported rows per day, with monthly budgets and a CSV download. (Admin › Usage) ## Give leaders answers without another status meeting Akollo AI reads the projects and updates each person may open and answers in plain language. Administrators decide who can use it. - “Which programmes are at risk this month, and why?” — Two: the HR system move is behind on data migration, and the ERP rollout was late on testing until Tuesday's update. Want a one-page summary for the steering group? - “Summarise this week's status updates from the southern region.” — Seven projects reported. Five are on track, one waits on a supplier and one needs a decision on scope. I listed the open decisions at the top. - “Who in the data team has room for the ERP rollout in November?” — Three people have more than a day a week free in November. Lena Brandt has worked on the ERP data model before. You decide who to book. Choose who may use AI, set a monthly limit per person and stop all AI requests at once. Run it on our cloud or on a model inside your own installation. It never widens anyone's access. ## Where large organisations usually start - [Projects & tasks](https://akollo.com/en/products/work) — Projects, portfolios and timelines. - [Resource planning](https://akollo.com/en/products/people) — Capacity across units and teams. - [Time tracking](https://akollo.com/en/products/time) — Timesheets with approvals per unit. - [Budgets & profitability](https://akollo.com/en/products/finance) — Cost and margin by department. - [Reports & dashboards](https://akollo.com/en/products/insights) — Reports, exports and BI datasets. - [AI assistant](https://akollo.com/en/products/ai) — AI under your own policy. ## Questions large organisations ask ### Can we roll out one department at a time? Yes. You decide which modules are enabled, and each unit can start when it is ready. Every new unit joins the same installation, structure and access model. ### Does Akollo work with our directory and sign-in? Yes. Connect your sign-in provider and directory, for example SCIM, Entra ID or LDAP. Directory changes start joiner, mover and leaver cases, and mass disables wait for an approver. ### Where can Akollo run? On our cloud, in your own cloud account or on your own servers. It is the same product in each case, the AI assistant included. ### Can our BI team read Akollo data? Yes. Reporting publishes datasets that BI tools such as Power BI read with a read-only key, or over SQL with a login that sees only the views opened to it. ### How do we prove who had access to what? Explain access shows every permission a person holds and where it comes from. Privilege and configuration changes are in the audit log, and access review results download with a checksum. ## Plan your rollout with us We will map your units, directory and first programmes, and agree which department goes live first. - [Book a demo](https://akollo.com/en/demo) - [Read the docs](https://docs.akollo.com/en) --- Source: https://akollo.com/en/solutions/enterprise · [Türkçe](https://akollo.com/tr/cozumler/buyuk-kurumlar), [Deutsch](https://akollo.com/de/loesungen/grossunternehmen)