The \u201cIndependent of Other Groups\u201d checkbox in the security group application is one of the most misunderstood concepts in Maximo. What is the significance of this checkbox? How does it affect the security authorization of the group? Let\u2019s have a look.<\/p>\n

<\/a><\/p>\n

As the name suggests, the \u201cIndependent of Other Groups\u201d checkbox on the main tab of the security group application specifies weather the group is independent of other groups or not. What that means is whether the authorization of this group can be merged with the authorizations of other groups. This is only applies to\u00a0multisite implementations, for single site implementation this checkbox doesn\u2019t have any significance. Lets understand how this works \u2013<\/p>\n

Scenario 1:<\/strong> Consider a multisite implementation; the user belongs to the 2 security groups with the following privileges:<\/p>\n

Group 1: Site A and Work Order Tracking application<\/p>\n

Group 2: Site B and Purchase Orders application<\/p>\n

If these security groups are both independent then the user ends up with rights for Work Order Tracking on Site A and Purchase Orders on Site B. If however the security groups are non-independent then the privileges combine and the user ends up with both Work Order Tracking and Purchase Orders on Sites A and B. Basically you sum up the privileges and if any of them overlap you take the highest level.<\/p>\n

Scenario 2:<\/strong> Consider a single site implementation; the user belongs to the 2 security groups with the following privileges:<\/p>\n

Group 1: Site A (or all sites authorization) and Work Order Tracking application<\/p>\n

Group 2: Site A (or all sites authorization) and Purchase Orders application<\/p>\n

Since there is only one site, irrespective of whether these groups are independent or non-independent the user will have the rights to both Work Order Tracking and Purchase Orders on Sites A.<\/p>\n

Scenario 3:<\/strong> Consider a single site implementation; the user belongs to the 2 security groups with the following privileges:<\/p>\n

Group 1: NO SITE and Work Order Tracking application<\/p>\n

Group 2: Site A (or all sites authorization) and Purchase Orders application<\/p>\n

If these security groups are both independent then the user ends up with rights for only Purchase Orders on Site A. This is because the two groups are independent and group 1 doesn\u2019t have authorization to any site hence user doesn\u2019t have rights to Work Order Tracking in Site A. If however the security groups are non-independent then the privileges combine and the user ends up with both Work Order Tracking and Purchase Orders on Sites A.<\/p>\n

NOTE:<\/strong> This is why the independent checkbox should not be checked for single site implementations.<\/p>\n

Scenario 4:<\/strong> Consider a multisite implementation; the user belongs to the 2 security groups with the following privileges:<\/p>\n

Group 1: Site A and Work Order Tracking application \u2013 Read, Route workflow Access<\/p>\n

Group 2: Site B and Work Order Tracking application \u2013 Read, Change Status Access<\/p>\n

If these security groups are both independent then the user ends up with rights for Work Order Tracking \u2013 Read, Route workflow Access on Site A and Work Order Tracking application \u2013 Read, Change Status Access on Site B. If however the security groups are non-independent then the privileges combine and the user ends up with Work Order Tracking – Read, Route workflow & Change Status Access on Sites A and B.<\/p>\n

Scenario 5:<\/strong> Consider a multisite implementation; the user belongs to the 2 security groups with the following privileges:<\/p>\n

Group 1: Site A and PO Limit of 10,000<\/p>\n

Group 2: Site B and PO Limit of 50,000<\/p>\n

If these security groups are both independent then the user ends up with PO Limit of 10,000 for Site A and PO Limit of 50,000 for Site B. If however the security groups are non-independent then the privileges combine and the user ends up PO Limit of 50,000 for both Sites A and B.<\/p>\n

Note:\u00a0<\/strong>Never change the MAXEVERYONE\u00a0group to independent group as this group has a lot of conditional grants which will stop working if this group is made independent without granting access to all sites (similar to Scenario 3).<\/p>\n

IBM Tech Note on why MAXEVERYONE shouldn’t be set as independent<\/a><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

The \u201cIndependent of Other Groups\u201d checkbox in the security group application is one of the most misunderstood concepts in Maximo. What is the significance of this checkbox? How does it affect the security authorization of the group? Let\u2019s have a look. As the name suggests, the \u201cIndependent of Other Groups\u201d checkbox on the main tab … Continue reading The Significance of \u201cIndependent of Other Groups\u201d in Security Groups<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[11,5],"tags":[],"yoast_head":"\n