Highlighted

Same package for different teams?

New Here ,
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?

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.

TOPICS
Creative Cloud

Views

12.8K

Likes

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

Same package for different teams?

New Here ,
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?

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.

TOPICS
Creative Cloud

Views

12.8K

Likes

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
Sep 26, 2014 2
Adobe Employee ,
Sep 26, 2014

Copy link to clipboard

Copied

Likes

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
Reply
Loading...
Sep 26, 2014 1
New Here ,
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.

Likes

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
Reply
Loading...
Sep 28, 2014 0
Adobe Employee ,
Jan 29, 2016

Copy link to clipboard

Copied

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.

Likes

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
Reply
Loading...
Jan 29, 2016 1