We are looking to extend our ArcGIS Enterprise environment to additional divisions of our company which operate in an only somewhat overlapping capacity. All of our users authenticate the same way (against our AD), and each division would (eventually) be generating some of their own content. There are not proprietary issues at stake here, but the challenge is more organizational in nature.
Are 'Groups' the right solution for this, or should we be thinking more about 'Sites' in Enterprise. Thanks!
Solved! Go to Solution.
While Sites is meant for organization of content, Sites itself won't control what content is available within the site. Sites are built off of groups, so you'd create a group for one division, and another group for a different division, and then you build the site around each group. The content available within each site is the content shared to each group. You can't have a site without a group.
So, you could rely solely on a group, but a group + Sites would give you that next level customization/divisional branding that may be appreciated.
While Sites is meant for organization of content, Sites itself won't control what content is available within the site. Sites are built off of groups, so you'd create a group for one division, and another group for a different division, and then you build the site around each group. The content available within each site is the content shared to each group. You can't have a site without a group.
So, you could rely solely on a group, but a group + Sites would give you that next level customization/divisional branding that may be appreciated.
This is helpful, thanks!