That's a really advanced concept, wow. Currently, the answer is no it can't. Thinking for the future, this would only work if there's a standard API that all other components call to determine whether the user is in a group or not, or to determine the list of groups that the user is in. If components ever get this info direct from the database, then this wouldn't work (because we don't want to actually change the group in the database, only dynamically in the current page view).

Another issue would be that some things get calculated before Chameleon would have the chance to add/remove groups. e.g. the routing of the current page. So if a group was not supposed to have access to a certain page, then this might be determined before Chameleon has a chance to modify the groups.

Anyway, amazing idea. If this is possible (in a future version of Chameleon) then it would help Chameleon to be able to affect even more things on your site: anything in any other component that can be affected by "group" could be dynamically controlled by Chameleon.

So I'm off to have a look at what might be possible...

Thanks,
Stephen