If the Zapier managed users list is missing from your account, do not assume that user access has disappeared. The interface may no longer provide a central list for managing everyone in the workspace. Instead, access is handled closer to the assets people need, such as shared folders containing Zaps and related resources.
The practical change is from central user administration to resource-level access management. To review or change access, open the relevant shared folder, inspect its members and permissions, then update the people who should be able to use the workflows stored there.
This approach can be clearer when folder structure reflects real teams and responsibilities. It can also create blind spots if nobody owns the access review. The right response is therefore not to search indefinitely for the old list, but to map important workflows to folders and verify access folder by folder.
What the missing Zapier managed users list means
The missing list usually indicates a change in where access is managed, not necessarily a loss of collaboration controls. In the older model, a central managed users view could make it easier to think about people first. In the current model described by the interface, the shared folder becomes the main access boundary.
That distinction matters. A person may need access to one group of automations but not to every workflow in the workspace. Managing membership at the folder level can support that narrower requirement, provided folders are organized around meaningful business responsibilities.
Access should follow the business resource a person needs to use, while ownership should remain visible outside the access setting itself.
Where Zapier access is managed now
Start with the shared folder that contains the Zaps or other assets a teammate needs. The exact labels can vary by account configuration and interface version, but the operating sequence is generally the same:
- Open the relevant shared folder in Zapier.
- Find its sharing, members or access controls.
- Review the people listed and the permission level shown for each person.
- Invite, change or remove members according to their current responsibility.
Shared folder membership answers who can access the resources in that folder. Permissions answer what each member can do. Folder structure answers which resources are grouped together. These are related decisions, but they should not be treated as the same thing.
A permission review is incomplete if it checks roles but not folder placement. A person with an appropriate role in the wrong folder may still have access to workflows outside their responsibility.
How to review and change members in a shared folder
1. Identify the folder that contains the required workflow
Do not begin by adding someone to every available folder. First identify the Zap, automation or related asset they need to use, then locate the folder that contains it. If the location is unclear, that is a workspace organization problem worth resolving before changing access.
2. Inspect the current member list
Open the folder’s access controls and review the visible members. Check names or email addresses, permission levels and any available options for inviting, editing or removing people. Use the current interface labels rather than relying on instructions written for the old managed users screen.
3. Apply the narrowest useful access
Add the person to the folder that supports their work and select the least powerful permission level that still allows them to complete their responsibility. Avoid granting broad access simply because it is faster. Broad membership makes later reviews harder and can expose workflows, data connections or business logic that the person does not need.
4. Record the reason for access
Zapier may show who has access, but the interface may not explain why that access exists. Keep a lightweight internal record of the folder owner, business purpose and expected members. This can be a short operations document or a field in an existing work-management system. The purpose is not bureaucracy. It is to make future changes easier to assess.
5. Recheck after role changes
When someone changes teams, stops supporting an automation or leaves the organization, review every relevant shared folder. Removing access from one folder does not prove that the person has been removed from every other folder that matters.
Designing shared folders for reliable access control
Folder structure is now part of your access model. A folder should have a clear business purpose and an owner who can explain who belongs there. Useful groupings may include marketing lead capture, sales and CRM workflows, customer support routing, finance operations or internal administration.
Use names that communicate function and scope. For example, a folder called Sales – Lead Routing is easier to review than one called New Folder 4. Naming should help a reviewer answer three questions quickly: what is in this folder, which team uses it and who should own access decisions?
Business responsibility
The folder contains workflows managed by one team or process, with a named owner and a predictable member group.
Convenience grouping
The folder contains unrelated automations because placing everything together seemed easier at the time.
A folder can be organized by team, process or project. The important rule is consistency. If one folder is based on department, another on a temporary project and a third on data sensitivity, users will find it harder to predict what access means.
A practical access review sequence
This sequence is more reliable than trying to recreate a single global list manually. It starts with business-critical workflows, so the review focuses attention where an access mistake could affect operations.
Hypothetical example: a sales automation folder
Imagine a company with a shared folder containing lead assignment, CRM update and sales notification Zaps. A marketing specialist needs to review lead capture, a sales operations manager owns the routing logic and a finance user needs no access at all.
Under a broad workspace-wide approach, all three people might be added for convenience. Under a folder-based approach, the team can place lead capture workflows in an appropriate folder, assign the sales operations manager as the owner and give only the relevant colleagues access. If finance later needs a reporting output, that requirement can be assessed separately rather than granting access to every sales automation.
The example is hypothetical, but the decision rule is useful: grant access based on the work a person is accountable for, not simply their department name or a previous membership list.
A shared folder should represent a meaningful operating boundary, not just a convenient place to store whatever was created recently.
Troubleshooting when access still looks wrong
You cannot find the old managed users page
Stop treating the old page as the source of truth. Open the folders containing the workflows you care about and review access there. If your organization has many folders, begin with business-critical automations and work outward.
A teammate cannot find a workflow
Confirm that the workflow is in the folder you expect, that the teammate is a member of that folder and that their permission level supports the required action. Also check whether the workflow was moved or reorganized after the original invitation.
A former user may still have access
Review all relevant shared folders rather than making assumptions from one folder. Keep a simple list of critical folders and their owners so offboarding reviews have a defined scope.
The team keeps creating duplicate folders
This usually signals an ownership or naming problem, not simply a user interface problem. Define who can create or restructure folders, what naming pattern is required and how a new folder’s purpose should be documented.
- Each critical workflow has a known folder.
- Each important folder has a named owner.
- Members are there for a current business reason.
- Permission levels match actual responsibilities.
- Folder names describe purpose and scope.
- Role changes trigger an access review.
When to get help with the wider automation system
A missing managed users list is often a symptom of a broader operating question: who owns each automation, where should it live and how should access be reviewed? If folders, permissions and workflow ownership have grown informally, changing individual members will only provide a temporary fix.
Process should come before tooling changes. Document the business states, owners and access rules first, then configure the workspace to reflect them. Automation can reduce repetitive work, but it cannot decide whether a person should have access unless that decision logic is already clear.
For help connecting Zapier workflows to a more deliberate operating model, see ConsultEvo’s Zapier automation service. Broader systems and process work is also covered through ConsultEvo’s systems and automation services.
Frequently asked questions
Why is the Zapier managed users list missing?
The interface may have moved away from a central managed users view, with access managed through shared folders instead. Check the folders containing the workflows and review their members and permissions.
How do I add someone to a Zapier shared folder?
Open the relevant shared folder, use its sharing or access controls, enter the person's details, choose the appropriate permission level and confirm the invitation if those options are available in your account.
How should Zapier folder permissions be organized?
Organize folders around clear teams, processes or projects, name an owner for each important folder and grant only the access required for current responsibilities.
What should I do if a teammate cannot access a Zap?
Confirm that the Zap is in the expected shared folder, that the teammate is a member of that folder and that their permission level supports the action they need to perform.
Need a clearer model for automation access?
If shared folders, workflow ownership and permissions have become difficult to manage, ConsultEvo can help map the operating process first and configure automation around clear responsibilities.
