• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

Same package for different teams?

New Here ,
Sep 26, 2014 Sep 26, 2014

Copy link to clipboard

Copied

Hi, we have several customers in the same enviroment/domain and we don´t want to create 4 different Photoshop CC packages (packaged exactly the same with Creative Cloud Packager).

If we use CCP with an generic Adobe Account and package these apps for Teams, can all our different customers login to the app with their own accounts or will we have some licensing problems?

Or do we need to package the apps and be logged in as a member of the team that are going to use the app?

TOPICS
Creative Cloud

Views

18.5K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jan 29, 2016 Jan 29, 2016

If you're doing a named-user deployment where each user signs in to license the software, then your approach should work fine. The sign in during package creation doesn't license the software, it just associates you with an organization so that the packager knows that you're entitled to deploy.

Votes

Translate

Translate
Adobe Employee ,
Sep 26, 2014 Sep 26, 2014

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 28, 2014 Sep 28, 2014

Copy link to clipboard

Copied

Hi and thanks for the reply.

I have read the links above but they doesn´t answer my question about using the same CCP package for different teams.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 29, 2016 Jan 29, 2016

Copy link to clipboard

Copied

LATEST

If you're doing a named-user deployment where each user signs in to license the software, then your approach should work fine. The sign in during package creation doesn't license the software, it just associates you with an organization so that the packager knows that you're entitled to deploy.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines