Selecting on information in a table can be done by filtering. Filters may reduce the amount of columns and the amount of lines.

Another way to solve the problem would be to create a page in the wiki dedicated to only one person.

The page can be based on a blueprint to make it easier to add new members and provide the information that is most relevant to the team. Information that should only be visible to team members in certain roles could be added on separate pages. The access to these pages is restricted by the wikis access control and are transcluded on the public page. Therefore the transclusion will only happen if the user has sufficient access to the restricted information.

You can add information in different formats. For instance the telephone number in form of its extension and in full format. You may also define different type of team members where different types of information is relevant.

To automtically render the information of all team members in tabular form, use the Display Table Macro. This macro allows you to query for team members with certain properties and select to show only the personal information that is relevant to your use case. That is you have the information of team members in one place and then have multiple views on this information by using the Display Table Macro.

To reference a single member you would need to reference a single line in the table.

If you have each team member on a separate page, the URL to that page references the team member. Via this URL all information about the team member that is relevant to the team is accessible. This URL can be easily added to other documents to create a web of information.

In tabular form it is often unwieldly to have short information like a name in the same line as a list of special interestes or other multi-line notes.

If the information for a team member is on a separate page, any information can be added. The projectdoc Toolbox distinguishes between Document Properties, which are typical single line and used to filter on team members for a search result and Document Sections which comprise multiple blocks like paragraphs or tables. Since each view selects on information, the information can be rendered in the most appropriate layout.

Having defined fields of expertise on could also collect names of team members who are provicient in that field. That is by clicking on an expertise on a team member page, the user would have access to a list of team members that also have knowledge in that area.

If you document projects and link to the people who are part of the team, a history of projects can be automaticall rendered on the team member pages. The same is true for topics the team members are authors of if they are mentioned as as authors on the topic page.