For some reason, since their launch, the fields that can be added to Members tab within a Team cannot be added to the library, or you cannot add fields that are already in the library, rendering these fields fairly ineffective and unusable.
Typical use case would be to apply the same fields to all Teams so they apply to every member in the entire org, like ‘Building location’ or ‘Office/room number’, ‘Floor’, ‘Desk phone / EXT no.’, ‘Position’, ‘Role’, ‘Manager’ etc.
Currently you need to manually add these fields into each Team, but as ‘copies’, i.e. unique instances. And currently the values only appear per team. If a member belongs to more than one team, you need to manually input the field value again. I really don’t understand why this limitation exists. ![]()
It would be great if you apply fields to Members as you can apply them to Tasks, and have the same behaviour as when a Task is multi-homed into multiple projects, the field values are the same, as long as the fields are added to the library. The same should apply when a member is added to multiple Teams - but this cannot be achieved without fields added to the library. ![]()
