A workspace hierarchy is the way your digital work environment is layered: the company at the top, then teams, then projects and processes, then the individual pieces of knowledge people use every day. A good one answers three questions without anyone asking: where does this belong, who can see it, and who owns it. The strongest setups also keep the reasoning behind the work next to the work itself, which is what Kept is built to do with its personal and business workspaces.
This guide is for team leaders, HR professionals, project managers and owners who need to organize a shared workspace so it still makes sense a year from now.
TL;DR
- Workspace hierarchy is the structure of your digital workspace (organization, teams, projects, folders, content). It is not the org chart, though it should reflect it.
- Keep it shallow. Create a new team when the people or the access needs change, and a new folder only when the way the work is organized changes.
- Set permissions high in the tree and let them flow down. Narrow access only where there is a real reason.
- Name things by what people would search for, then test the labels with the people who will use them.
- Structure tells people where things live. It does not tell them why work is done a certain way. Plan a place for that reasoning too.
Table of Contents
- What workspace hierarchy means (and what it does not)
- The levels of a workspace hierarchy
- Where to split: new team, new folder, or new workspace?
- Organize by how people look for things
- Naming, ownership and permissions
- What a hierarchy cannot hold on its own
- Build a hierarchy that supports onboarding and continuity
- Common problems and how to fix them
- Review and improve your hierarchy as work changes
- Where Kept fits
- Our perspective
- FAQ
- Sources
What workspace hierarchy means (and what it does not)
Two phrases get mixed up here.
Workplace hierarchy is who reports to whom: leadership, department heads, managers, and the people doing the work. It describes authority.
Workspace hierarchy is how your tools organize content and access: which spaces exist, how they nest, who can open them. It describes information.
The two should relate, but they are not the same thing. Research from MIT's Center for Information Systems Research on a large digital workplace program found that in digital work, networks and influence can take precedence over formal hierarchy. A later MIT Sloan Management Review piece reports that relational needs such as information, task resources, recognition and leadership can sustain manager and employee relationships in virtual settings without leaning only on formal position.
The practical lesson: if you copy your org chart straight into your workspace, you build walls where your work actually crosses lines. A support lead, an operations manager and a new hire may all need the same refund process. Your structure should serve how work flows, not just who sits where.

The levels of a workspace hierarchy
Most digital workspaces end up with some version of the same five levels. One published team-organization guide describes them as an organization, optional workspaces that group related teams, teams, folders and files. Translated for process and knowledge work, it looks like this:
| Level | What it is | Typical example | Who usually owns it |
|---|---|---|---|
| Organization | The whole company account | Your company | Owner or executive sponsor |
| Workspace group (optional) | Related teams bundled together | Operations, Customer, People | Department head |
| Team workspace | One team's shared home | Support, Finance, Field Service | Team lead or manager |
| Project or process area | A body of work with a purpose | Onboarding, Month-end close, Returns | Process owner |
| Item | The document, process or answer itself | One documented process | Whoever does the work |
Notice that the middle levels mirror your layers of leadership, department heads and managers, but the bottom level is where the people doing the work live. That is the level most often neglected, and it is the one new hires and colleagues need most.
Research gives a second lens. A 2022 peer-reviewed study of enterprise collaboration systems built a typology of workspaces with three broad categories (community, team and non-work-related) and five workspace types. For a business, the useful takeaway is that spaces have different purposes. A team's working space, a company-wide community space and a social space should not be governed the same way.
Where to split: new team, new folder, or new workspace?
The most common mistake is creating structure because you can. A simple rule keeps it honest. The same team guide suggests creating a team when collaborators or access needs change, and a folder when the way the work is organized changes.
Apply it as three questions:
- Do different people need to work here? If yes, you probably need a separate team workspace.
- Do different people need to see it? If yes, you need a separate access boundary, which means a team or a restricted area.
- Is it the same people with the same access, just a different topic or stage? Then use a folder or project area inside the existing workspace.
A 40-person company might end up with four team workspaces and a handful of project areas in each. A 2,000-person company might add a layer of workspace groups by department. Neither needs more than four or five levels. If someone has to click seven times to reach a process, the structure is working against them.
Organize by how people look for things
The structure only works if people can find things in it. The Nielsen Norman Group's research on intranet information architecture covers several ways to group content: by department, topic or task, audience, geography, format, time, or alphabet. Their research draws on organizations in 13 countries, from small ones to those with more than 20,000 employees, so the patterns hold across sizes.
For process and knowledge work, a few guidelines tend to hold up:
- Group by task before department. "Handle a refund" is easier to find than "Finance, Section 3."
- Use the words your people use. If the floor calls it a "walkthrough" and the handbook calls it a "commissioning protocol," label it both ways or pick the floor's word.
- Avoid duplicates. When the same process lives in two places, one of them goes stale. Keep one home and point to it.
- Keep labels plain. Clever names and internal acronyms are the first thing a new hire cannot decode.
Show work states, not just topics
Folders can also tell people how finished something is. The same guide gives an example of separate Production, In progress and Archive folders, with WIP, Review and Shipped as a common stage pattern that teams can extend to fit their own process. For documented processes, the equivalent is simple: draft, reviewed and current, plus an archive for the old way. A reader should never wonder whether the version in front of them is the one to follow.
Naming, ownership and permissions
Three habits keep a hierarchy from decaying.
Consistent names. Pick a pattern and write it down: area, then process, then audience, for instance. Consistency matters more than which pattern you choose.
A named owner at every level. Every team workspace and every process area needs a person who is responsible for keeping it accurate. Without an owner, a space becomes a pile.
Permissions set high, narrowed deliberately. Access should flow down the tree. In the team guide, subfolders inherit access from their parent folder, and access can be narrowed or the folder made private when there is a reason. That inheritance model is worth copying in your own thinking: set the default at the team level, then restrict only what truly needs it, such as compensation processes or customer-sensitive handling. Every exception you create is one more thing an admin has to remember.
If you want a concrete admin routine, our guide to workspace roles and the permission checks admins can verify walks through what to confirm and how often.
What a hierarchy cannot hold on its own
Here is the gap most structure guides skip. A tidy tree tells you where a process lives. It does not tell you:
- why the team does it that way,
- when the standard way does not apply,
- who has handled the unusual cases before,
- or what the numbers in your systems mean for that step.
Your layers each hold a different piece. Leadership holds the why. Department heads hold how departments connect. Managers hold the judgment calls and who does what. The people doing the work hold how it really runs. Folders do not join those pieces. They only sort the pages.
This is why we suggest treating the bottom of your hierarchy differently. At the item level, record decisions and exceptions, not just steps. Our piece on capturing decisions, not steps shows what that looks like in practice, and the five-layer knowledge base architecture post covers how to stack that reasoning on top of the structure you already have.
Build a hierarchy that supports onboarding and continuity
Onboarding is the fastest test of any workspace structure. If a new hire can open their team workspace on day one and find the five processes they will touch first, the hierarchy is working.
A workable sequence:
- Start with the team workspace, not the company. New hires need their own team's processes before the full company picture.
- Create an onboarding area inside each team. List the first-week processes in the order they will be needed.
- Link the exceptions. Next to each process, keep the cases where the usual approach changes and the reason why.
- Mark an owner for each process. Newcomers learn quickly who to ask when the name is on the page.
- Plan for handoffs. When an expert changes roles or leaves, their processes should already live in the shared space. Our expert handoffs use case shows how teams keep that continuity.
For remote and distributed teams the same logic applies with extra weight, since nobody can lean over a desk to ask. Our guide to remote process documentation covers how distributed teams handle it.
Common problems and how to fix them
| Problem | What it looks like | Fix |
|---|---|---|
| Excessive nesting | Folders inside folders inside folders | Cap depth at four or five levels; flatten the middle |
| Duplicated content | Same process in two team spaces, different versions | One home per process, links elsewhere |
| Unclear access | People unsure who can see what | Set defaults at team level, list exceptions in one place |
| Confusing labels | Internal jargon, vague names like "Misc" | Rename using the words people actually search |
| No owners | Stale pages nobody updates | Name an owner per area, review on a schedule |
| Org chart copy | Walls where work crosses teams | Organize by task, link across teams |
The Nielsen Norman Group's report covers confusing labels, unclear terms, navigation and information architecture problems as the issues that most often trip up intranets, and the list above is the same family of trouble at team scale.
Review and improve your hierarchy as work changes
A hierarchy is never finished. Teams merge, products change, and the way work gets done shifts. Set a review rhythm, quarterly for fast-moving teams and twice a year for steadier ones, and use real input rather than guesses.
The same research describes methods for gathering that input: surveys and card sorting, and tree testing and user testing as further information-architecture methods. You can run a lightweight version yourself:
- Card sort. Write each process on a card, ask five people from different roles to group them and name the groups. Compare with your current structure.
- Find-it test. Give three people a task ("find how we handle a late delivery") and note where they click first.
- Owner check. Ask every owner whether their area is still accurate. Archive what is not.
Then adjust. Small, regular changes beat a big reorganization every two years.
Where Kept fits

Kept offers a personal workspace and a business workspace, with workspace-level access controls so each team sees what it should. Capture is opt-in, and people can review and delete what they have shared. Instead of filling a tree by hand, people describe how they do their work in their own words, and guided conversations bring out the exceptions and the reasoning behind them. Search is context-aware and answers come with citations, so a new hire can ask a question and see where the answer came from.
Kept also connects to the systems you already run, so the reasoning is linked to the numbers that work touches. See how that works in our systems you already use use case, or explore Kept for Business. When you are ready to set up workspaces for your team, the pricing page lists the personal and business plans.

If you are starting small, a team lead can begin with a few processes in a personal workspace. Our guide on capturing 3 to 5 processes shows the first steps, and the four-hour team playbook guide shows how to turn them into something a whole team can use.
Our perspective
Most companies treat workspace hierarchy as a filing problem. We see it as a connection problem.
A company is its people, the work they do, and the systems that record that work. Today those three are stored apart. The systems hold the numbers. The people hold the reasons. A folder tree sorts the pages, but nothing in it holds both.
That is why we built Kept to talk with people at every level and connect to your systems. For each piece of work, it holds what is done, why it is done that way, when that way applies, who does it, and the evidence behind it. Your hierarchy then becomes the connective tissue of your company, not just a map of folders.
Taking part is each person's choice, and nothing a team says is used to train AI. The company sees where people do the same job differently and decides what becomes its own way. The longer a team runs on Kept, the more it knows.
Anthony
FAQ
What is a workspace hierarchy?
It is the layered structure of a digital work environment: organization, optional groups of teams, teams, projects or folders, and the items inside them. It controls where content lives and who can access it. It is separate from your org chart, though the two should inform each other.
How many levels should a workspace hierarchy have?
Most teams do well with four or five: organization, team, project or process area, and item, plus an optional group level for larger companies. If people need to click through more than that to reach a process, flatten the structure and rely on search and links.
Should I organize by department or by task?
Start with the team workspace for access and ownership, then organize inside it by task. People look for how to do something, not for the department that owns it. Cross-link processes that span teams instead of copying them.
How should I handle permissions?
Set access at the team workspace level and let it flow down. Restrict only the areas that truly need it, and keep a short list of those exceptions so admins can check them. Our workspace roles guide gives a verification routine.
How often should I review my workspace structure?
Quarterly works for fast-changing teams and twice a year for steadier ones. Use a card sort or a simple find-it test with a few people from different roles, then fix labels, owners and duplicates.
Sources
- The Digital Workplace Transforming Business, MIT CISR
- Relational Power Is the New Currency of Hybrid Work, MIT Sloan Management Review
- Team, folder, and file organization
- A Workspace Typology for Enterprise Collaboration Systems
- Intranet Information Architecture (IA) Design Methods, Nielsen Norman Group
