Managing a Wrike account with 200, 300, 400, or more users is a different challenge. The decisions made at the beginning of the setup become very expensive to undo later.
An admin managing around 300 users in Wrike, where the account has grown to include multiple teams and several levels, is typically trying to figure out how to give teams enough freedom to work and keep the overall account structure intact. Here is how to approach it.
Roles and permissions
The standard Wrike licence types, Full, Editor, Limited, and Collaborator, cover most situations. Some organisations add a layer on top of that. You could create an additional role called Project Manager internally. These users get more rights in the projects they own, particularly around changing dates, since they own the timeline. In other projects they are not leading, they operate as standard editors without the ability to change dates.
Full admin access is reserved strictly for administrators, and admins are the only people who can delete tasks.
When everyone has full access, nothing is protected. When nobody has enough access, nothing moves. The goal is to give people the right level for their role.
Organising by space, not by person
For larger accounts with multiple business units or divisions, the most functional structure is organising Wrike by what might be called “company sides,” business divisions, each with its own spaces and its own responsible admin. Each division can have up to 100 users in its own spaces, with a main admin responsible for the working structure within those spaces.
At the account level, a small group of senior admins can see across all spaces. They are not in every space doing daily work. They have a high-level view that lets them see when something has gone seriously wrong.
Within each division, how teams use Wrike can vary significantly. An R&D team might run strict project management with workflows. Another team might use a simple Kanban board with little planning. Wrike can accommodate both in the same account, which is one of its strengths, as long as the spaces are organised clearly enough that the two approaches do not bleed into each other.
Have a centralised governance space
One of the most practical things a large-account admin can do is create a dedicated Wrike Governance space, a space where all Wrike-related communications are. Change requests, configuration decisions, training materials, and account updates from Wrike all stay there. This keeps Wrike information in one place and reduces the situation where important account decisions are spread across emails, Slack, or Teams.
Account-level custom fields and workflows should be reviewed periodically to determine what belongs at the account level versus what should be space-level.