Shared files become difficult to manage when personal uploads, client work and team projects all sit in the same place. A Media2URL team workspace gives a project or group its own media library, so those files stay separate from a member's personal workspace.
People invited to the workspace can work with the shared files according to their assigned role. The active workspace also determines which library and available controls appear in the dashboard.
A team workspace changes more than where a file is stored. It also changes which shared library is open and what a member can do inside that workspace.
The normal workflow starts by choosing the right workspace, then inviting the people who actually need access.
Create a team workspace for the project or choose an existing one from the workspace switcher. Changing the active workspace also changes the shared library you are working in, while personal files remain separate.
Workspace administrators can invite members by email and assign an available role. Invitations are tied to the workspace rather than to one file URL.
Files uploaded while a team workspace is active belong to that workspace context. Members can then work with the shared library according to the actions allowed by their role.
Team access does not have to stay the same forever. Owners and permitted administrators can review member roles, cancel pending invitations or remove access when someone no longer needs the workspace. Recorded workspace and file actions can also appear in the activity area where logging is available.
A workspace is not simply another folder. A folder helps organise files inside a library, while a workspace creates a broader boundary for the people, shared files and permissions connected to that project.
This matters when one account is used for more than one type of work. An agency may have files for several clients, while a small team may want company assets kept away from personal uploads.
When the active workspace changes, the dashboard moves into that workspace's library and permission context. This is why checking the workspace switcher is useful when a file appears to be missing.
The workspace switcher is the first control to check when a file seems to be missing. It changes the library and the permissions context used by the dashboard.
Personal uploads stay separate from files stored inside a team workspace. A member who belongs to more than one workspace can switch between the available contexts from the dashboard. This separation becomes useful when the same person handles personal files as well as client or team projects.
Not everyone working on a project needs the same level of control. Media2URL uses Owner, Admin, Editor and Viewer roles so workspace access can reflect what each member is expected to do. A person preparing files may need editing access, while someone checking the final asset may only need the narrower controls available to a Viewer.
Team membership changes over time. A permitted administrator can invite someone, cancel a pending invitation, change an available role or remove a member when that person no longer needs access. Removing a member affects that person's workspace access. It does not delete the shared files for everyone else in the workspace.
The activity area can help when you need to understand what changed inside a workspace. Where records are available, actions such as file or membership changes can appear in chronological order. These records describe activity inside the workspace. They are different from visitor analytics for people opening a public link.
| Role | Practical purpose |
|---|---|
| Owner | Holds the main workspace control and membership responsibility. |
| Admin | Can handle permitted workspace and member management actions where available. |
| Editor | Works with shared media and the editing or organisation actions allowed by the workspace. |
| Viewer | Uses a narrower access level for inspecting and working with the available shared assets. |
The exact controls available to each role can depend on the workspace and plan, so the dashboard remains the guide for the current account.
A team member does not need more control simply because they are part of the project. The safer and usually simpler approach is to give people the role that matches the work they actually need to complete.
For example, someone preparing campaign images may need editing access, while a client checking approved files may need a narrower role. If responsibilities change later, the role can be reviewed instead of leaving old permissions in place.
This general approach follows the principle of least privilege: access should be limited to what someone needs for the task. Role based permissions are also common in established digital asset systems because different users often need different levels of control over shared files.
Workspace membership and file ownership are separate concerns in the team workflow. When someone leaves a project, removing their workspace access does not mean the shared project files should disappear with them.
This becomes especially important for client work or long running projects. A team may need the existing PDFs, images or download links after the person who originally uploaded them is no longer involved.
Files should be removed through their own library or account controls when deletion is actually intended. Member removal should be used for changing who can work inside the workspace.
A shared workspace becomes harder to follow when several people can make changes. If a file has moved or a member's access has changed, a chronological activity record can provide context about what happened inside the workspace.
Activity history should not be confused with public link analytics. One helps explain actions taken inside the team workspace, while the other would describe how recipients interact with hosted links.
Give a client project its own workspace when the same team handles files for several accounts. Images, PDFs and downloadable files can stay with that client instead of being mixed into another project's library.
A content editor can prepare the files while another member checks the current asset with a narrower role. The workspace owner keeps responsibility for membership and the available workspace settings.
A campaign may involve designers, marketers and someone responsible for the final review. Keeping its media inside one workspace makes it easier for those members to work from the same library without mixing the campaign with unrelated uploads.
A small business can keep shared product images, brochures or customer facing files inside a team workspace instead of asking everyone to use the same login. Each invited member can use the role available for the work they actually need to do.
| Dimension | Main purpose | Who it affects |
|---|---|---|
| Team workspace | Separates a shared project, library and member access context | People working inside the Media2URL dashboard |
| Folder | Organises related files inside a library | Members who can access that library |
| Share link | Gives access to a particular hosted file or sharing page | The recipient opening that link |
A workspace role does not automatically make a public file private. Workspace membership controls what a member can do inside the dashboard, while the file's own sharing settings determine how its public or restricted link behaves.
Before assuming a file was deleted, check which workspace is currently active in the dashboard. Switching from a team workspace to the personal workspace changes the library you are looking at.
If the workspace is correct but the file still does not appear, the next things to check are the member's current role and the file's location inside the shared library.
Yes. The dashboard workspace switcher lets a signed in user change the active context. The selected workspace controls which library and permissions are shown.
The workspace implementation supports Owner, Admin, Editor and Viewer roles. Which role can be assigned or changed depends on the actor's permissions.
The member loses access to that team workspace. The shared files remain in the workspace unless an authorized user separately moves them to Trash or deletes them.
No. Workspace quotas and plan rules can differ. Use the current dashboard and pricing information for the limits attached to your account.
A team workspace keeps shared project files in a separate library context and lets invited members work with them according to their available roles. It is useful when several people need access to the same media without mixing those files with personal uploads.
No. A folder organises files inside a library, while a team workspace also creates a broader member and permission context around the shared library.
No. Removing a member removes that person's workspace access. Shared files remain in the workspace unless they are separately removed through the available file management controls.
No. A workspace role controls dashboard access for that member. Public, private or other link behaviour is controlled separately through the available file sharing settings.
Next steps
