Creating new Site (Project vs Page)

[#1]

New to Community and AEM 🙂 and this feels like 101 question, but have read up an searched but did not find any real info on Project Benefit of using it. (I did find info on how to create, issue etc.) 

Our current structure we have numerous sites. Each sites was create by creating a page and then building from there. One of the main issues is that all users can see all the sites, etc so there is risk that marketing person can accidentally change another brand's site. I was wondering if this was something we can solve with Project. 

Therefore what is the benefit of creating a site within a Project instead of creating from a page. 

[#2 · Accepted solution]

@Elbie47,

You can create a user group for each site by providing specific access rights to the group from (touchUI)http://localhost:4502/libs/granite/security/content/groupadmin.html or (classicUI) http://localhost:4502/useradmin. Next, you can assign a user as a "member" of that group.

Since your user group has only read,write,delete access to /content/brand/site-a, only those members of the group can read,write,delete /content/brand/site-a.

You can automate the creation of groups using Cognify's APM tool https://github.com/Cognifide/APM or B, using Netcentric's Acess Control Tool https://github.com/Netcentric/accesscontroltool.

Documentation on how to create a group: https://docs.adobe.com/content/help/en/experience-manager-64/mobile/administering-phonegap/configure...

[Elbie47]

Hi @Elbie47 

You can restrict the user(author) to see limited content as per your requirement by creating usergroups in aem and create/move users under that usergroup.

Please go through these links

https://helpx.adobe.com/in/experience-manager/6-3/sites/administering/using/security.html

https://helpx.adobe.com/experience-manager/6-3/communities/using/users.html

Regards,

Arpit

[Elbie47]

Thank Arpit, Do you have knowledge on benefits why use Projects instead of single page?

[#5]

@Elbie47 

     As @BrianKasingli  and @ArpitVarshney  mentioned, the primary way to solve your problem is to provide correct access restrictions to the users . You have to create correct set of groups for your content authors/ managers and set permissions for them to the correct set of pages so that they won't be able to access the pages which they are not intended to. Rest of how to create groups and manage the same are mentioned in the above answers. 

   Noe coming to your other question of Project vs Page , project is nothing but a grouping of your resources. I am not sure if you got a chance to go through this link https://docs.adobe.com/content/help/en/experience-manager-65/authoring/projects/projects.html . If not , please read through and it might give you a clear overview and understanding on projects. Even while using projects, the permission control should be done via users and groups. 

 As mentioned in the about link 

When you create the project and add users to the various roles, groups associated with the project are automatically created to manage associated permissions. For example, a project called Myproject would have three groups Myproject Owners , Myproject Editors , Myproject Observers . However, if the project is deleted, those groups are not automatically deleted. An administrator needs to manually delete the groups in Tools > Security > Groups .