Pre-pending a workspace, search or datasources name with [teamname]. will result in only that specific team having access. Not only will they not be able to access these Workspaces, searches and datasources, they won't even be able to see that they exist. At the same time it is understandable that there are resources that are common between the entire organisation as such it is still possible to simply have resources that are available to everyone as admin accounts are able to save into the global namespace by not appending a team. However, this functionality is only enabled when running a licensed Logscape Manager, teams are still creatable without the license, but visibility won't be controlled as you'd expect!
For example I'm setting up an environment in which two teams, A and B will be working.
I obviously don't want them seeing all of each others work, there is sensitive data in there. So using Logscape's Multi-tenancy capability I'm going to segregate their environments.
In order to limit visibility to only my team, Logscape will automatically pre-pend my resources with my team name
I.e I could name a workspace
TrendingPrices
And Logscape would automatically save this as A.TrendingPrices, All members of team A would be able to see this, but team B would not.
The same technique can be applied to Datasources and Searches,
B.UnixApp B.UnixMachineSearch
However, even in environments where data needs to be segregated, you may want to share some data, such as metrics about the health of environment. Admins are able to save a resource without a team, thus allowing global visibility.
HomepagesLogscape comes with a default homepage, however you can override this on a per team basis by simply naming the workspace.
TEAMNAME.home
