cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP Enable Now Creating the Content structure

PascalWissler
Explorer
0 Kudos
771

structure-in-manager.pngHello everyone,

I just have a question regarding creating a content structure in a collaborative scenario. I assume that you need to create the content structure like "creation" "maintenance" and "published content" first within manager for each workarea so that every author can access this structure when he or she is creating or working on content via producer. (via check out all objects in Producer...)

If you only create this structure in producer the structure will only be shown on the local machine of the corresponding author.

Or how sould the best practice process look like? Thanks in Advance for your help.

Accepted Solutions (0)

Answers (2)

Answers (2)

KristinaKunad
Product and Topic Expert
Product and Topic Expert

Hi Pascal,

the first group you see in a fresh Producer is only a local group. Please check this Info Center page to see how to check out content located on the manager and set up a cloud author workspace.

Once you have checked out groups from the manager, you see that one group doesn't have an icon (local group) and the other has a cloud icon (managed group). The managed group can be seen by other authors, the local one cannot.

There's a lot more to say about structuring, you can look at the Info Center to find out more.

I hope this explains it, if so please mark the question as answered.

Take care,

Kristina

DirkManuel
Active Contributor

I also created a video on first login to producer here, and an article on structuring your workarea (and the selective synchronization Kristina mentions) here.

DirkManuel
Active Contributor

If you create it in Producer, and Save to Server, all other Authors will see it as soon as they re-synchronize / update from server. I try to encourage Authors to re-synch at least when they first access Producer for the day.

(I also don't particularly like separate Creation / Maintenance / Published Groups, but that's a separate discussion!)