Skip to main content
Attribute mapping is only possible in combination with an active single sign-on (SSO). After activating SSO, the desired attributes or groups can be released through the SSO application (e.g. Entra ID, Shibboleth, SAML2). When a user signs in, we then receive the attribute information in addition to the name and email address. Examples: attribute: Department 01, group: IT-DEV, status: Student / Staff Test which attributes and groups are passed along through your SSO sign-in. You can view this under SSO & Security - Load my attribute data.

​
What is attribute mapping?

With attribute mapping, you can assign user properties from your IdP (user management) to anny communities. This way, members can automatically be added (auto-join) to their respective internal booking areas (communities). Where do I make the setting?
  1. Click your account settings
  2. Select the SSO & Security section
  3. Scroll down to Attribute Mapping
  4. Click Add mapping
You can assign 10 different attributes in total. The assignment to a community is used most often.
  • Communities
  • Roles
  • Profile picture
  • Language
  • Login allowed
  • Identifier
  • Email
  • Last name
  • First name
  • Display name
Attribute mapping overview

​
Create a rule

  1. Click Attribute Mapping and select Community
  2. Click Rule to create a new rule
  3. Enter the value of the group or attribute in the condition and define the community the users should be added to. Example M365 Entra ID groups: If http://schemas.microsoft.com/…/identity/claims/**groups** contains (array): gruppe_dev Then anny community Dev Team Office Example Shibboleth: If: urn:oid:xxxx contains (array): Student Then anny community Students Wave University
  4. Save your entries
Entering the values for group names and value is case sensitive and must exactly match the spelling passed by the IdP. The exact spelling can be viewed under ‘Load my attribute data’.
Are there multiple values that belong to a specific group of people? The system runs through all rules. Whenever a rule matches, that value is applied.
A person belongs to a department (e.g. Sales) within a company. As a user in anny, they should therefore automatically be added to the communities “Sales and Marketing”, “Retail”, and also “Company”.
A person belongs to a specific degree program (e.g. Philosophy Teaching) within a university. As a user in anny, they should therefore automatically be added to the community “Philosophy Teaching”, but also to the communities “Faculty of Philosophy” and “Teststadt University”.
Rule example

​
Add all users of your company (SSO)

Create a new rule for community mapping and then delete the condition. Select the community you want all users of your company to be assigned to. Add all users Now all users of your SSO are added to the desired community without any filter.

​
Technical details of the assignment

Pro tip: If there are users who belong to multiple groups in M365, the group attribute is an array. That means you should use the “contains (array)” operator instead of “equals”.