IMPORTANT... BUG? - New feature of control by FCRM Tags
Hello team and Shahjahan Jewel
Just noticed this:
- If you start using the control by tags, it works like magic!
- BUT, if a user has a pending approval for a space and you are now using control by tags and accept that request, the user will join.
- Moreover, if you rely afterwards on adding or disabling the tag for that user, that user will still be on the space and has to be manually removed.
Is this intended?
Just though I have to share that so as, if we are relying on tags for control, this does not apply when the user is manually added and later tags are added.
eg.: I would like to be able to manually add users of course... but for example if I add a control tag for that user and want to rely on it to control afterwards, will like it to know this :)
Jorge de los Reyes, Shahjahan Jewel Just wanted to test my understanding of the new frcm control tag feature....my understanding is that if you map a tag to a space or a course in fluentcommunity access management settings, then regardless of how the contact is added to the space or course (becomes a member), the tag will be applied to the contact- whether manually adding the tag to a contact in frcm, with frcm automation, or manually adding a contact in fcommunity, etc. However, if the tag is not mapped, then the tag behaves like a "regular tag". If my understanding is correct, then this is a desired behavior for my use case.