> For the complete documentation index, see [llms.txt](https://tsanet.gitbook.io/connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tsanet.gitbook.io/connect/documentation/getting-started/member-success/roles-for-members.md).

# Roles for Members

The image below shows the roles that Members have with TSANet

<figure><img src="https://160382229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFnKqXLEByXxXehD4FNIm%2Fuploads%2FMcPWndE7UI265Y4vocJj%2Fimage.png?alt=media&amp;token=7852fcc0-59ef-4ecd-969e-abb7a1d147c5" alt=""><figcaption></figcaption></figure>

**Notes about roles:**

* In small organizations, one person can have multiple roles
* The time a person spends with TSANet is small.  Decision-making and integrating TSANet into existing processes are done during the onboarding phase.

**Business Manager:**

The Business Manager is a senior-level position within the organization that provides executive sponsorship.   Example titles are (Chief Customer Officer, VP Support, VP Customer Success, and VP Partnerships).   This person approves budgets and removes roadblocks for program managers.

**Program Manager:**

Program managers implement TSANet within their existing processes.  Some examples below:

* Partner Manager adding TSANet onboarding of Partners as part of the certification phase
* Support  Process integrating TSANet as part of the escalation and collaboration (swarming) process
* Support Planning, integrating TSANet into the OEM and Solution Support process
* IT Project Manager implementing the TSnet Connector within their CRM system

**Key User:**

The key user has a role in the operations.  They are the point of contact for change management and feedback to TSANet and Program Managers.   Support Managers and Escalation Managers are a good fit as a TSANet Key User.