Skip to main content
marks59391491
marks59391491
Participating Frequently
January 4, 2018
Answered

Is there a way to make a group with access to shared projects?

  • January 4, 2018
  • 2 replies
  • 739 views

So I'm running through the idea of introducing team projects at work and trying to see where there might be potential issues. One of the things I've come up against is how people are able to become collaborators on projects.

Hypothetically, if the project owner is absent, or no longer works at our company - how would a new team  member access the projects?

    • Is there a way to have a default group maybe where everyone on the team has access to all shared projects?


      Also, I'm a bit worried about how our shared projects are organised in the browser - will it always just make a big list of projects that you are a collaborator on? Or is there a way that you'd be able to browse for projects in the usual way and click on a project file to open it?
    This topic has been closed for replies.
    Correct answer PeterELee

    Anyone who has access to a Team Project can invite other collaborators, not just the person who created the Team Project, so you should be fine as long as other people were collaborating on the same Team Project. Also, in a Team or Enterprise environment, I assume that there is an administrator who could reassign the departed team member's Adobe ID if needed.

    As far as organization in the Browser, yes, it's a flat list at the moment. We're thinking about additional tools to organize it in the future, but for now that's the only interface for opening Team Projects. You can remove Team Projects that you no longer care about from the list by archiving ones that you created, or removing yourself as a collaborator from ones that someone else created.

    2 replies

    PeterELee
    Adobe Employee
    PeterELee
    Adobe Employee
    January 4, 2018

    Glad to help. Note that all of your work is stored to a local database on your workstation first, and only synchronized with the cloud when you're connected. There are also commands in Premiere to export your work to a local .prproj and to convert a standalone project file to a Team Project (plus corresponding commands in After Effects).

    PeterELee
    Adobe Employee
    PeterELeeCorrect answer
    Adobe Employee
    January 4, 2018

    Anyone who has access to a Team Project can invite other collaborators, not just the person who created the Team Project, so you should be fine as long as other people were collaborating on the same Team Project. Also, in a Team or Enterprise environment, I assume that there is an administrator who could reassign the departed team member's Adobe ID if needed.

    As far as organization in the Browser, yes, it's a flat list at the moment. We're thinking about additional tools to organize it in the future, but for now that's the only interface for opening Team Projects. You can remove Team Projects that you no longer care about from the list by archiving ones that you created, or removing yourself as a collaborator from ones that someone else created.

    marks59391491
    marks59391491Author
    Participating Frequently
    January 4, 2018

    Okay thanks. Currently I'm torn between how handy  the version history etc is, and getting my head around the abstraction with the projects being in the cloud..

    I've got a few other little questions that I've stumbled across as I've gone through using the team projects workflow, so no doubt I'll be back with more queries

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices