# Setting-up Player Features

## 🧭  Navigation

![](https://3654650655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGrxN2ttYCb8JwJc2TS%2Fuploads%2FaaTHXU7LXmIQl2rO6IU8%2FScreenshot%202024-06-20%20at%2017.11.26.png?alt=media\&token=76e04662-6347-4e9a-8fc3-b5c5f8364626)

Navigate to the Player Features from the **Menu -> FT Singularity Model -> Features -> Player Features.** 

From the Player Feature page, select the **New Player Feature CTA** from the top-right hand corner to create your own Player Feature.

{% hint style="info" %}
 🧠  **Remember that you can use any of the system features that come as part of the Singularity Model, but you cannot edit them.** 

If you want to make changes to system features, you can set up your own. 
{% endhint %}

## 📇  Feature Settings

Once inside a new or existing Player Feature, you will find the **feature name** and **description** and the **possible outcome** details. 

#### **Feature Name and Description**

**Name** - Enter a descriptive name to identify the Player Feature.

**Description** - Define what the Player Feature refers to in a detailed description. In the example below, the description reads '*The current lifestage of the player, an active player is anyone with a real money transaction in the last 30 days*'. 

This helps to understand what is being calculated and how it is defined. 

![Feature Settings: Name and Description](https://3654650655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGrxN2ttYCb8JwJc2TS%2Fuploads%2FTUonqCIKbWwVz9IsN37I%2FScreenshot%202024-06-20%20at%2017.15.19.png?alt=media\&token=1f398f7c-498b-4f59-8400-13f3fd3d5e7c)

#### Possible Outcomes 

**Feature Type** - Every Player Feature must be attached to a Feature Type. Select the associated Feature Type from the drop-down menu and the table below will be populated with the classes that have been set for that Feature Type. 

Read more about Feature Types and their Classes [**here**](https://fast-track.gitbook.io/knowledge-base/~/revisions/aNUpux3obVYekyrny3V7/the-singularity-model/feature-types)**.** 

**Default Value** - Set a default value from the drop-down menu if you want your players to be assigned to a specific class by default. This is the value they will be assigned if they have not yet been classified as any other value. 

**Is Multi-Class?** - Select this check-box if you want it to be possible for a player to belong to more than one class at a time. In the example in the image below 👇, a player can only belong to one Lifestage at any one time. A player cannot be classified as Active and Inactive at the same time. Therefore the 'Is Multi Class' check box is not selected for this example. 

{% hint style="info" %}
**An example of a Player Feature that would be considered as multi-class is Opted-in Channels**. This is multi-class because a player can be opted-in to more than one channel at the same time. 
{% endhint %}

![Feature Settings: Possible Outcomes](https://3654650655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGrxN2ttYCb8JwJc2TS%2Fuploads%2Fp9SJpUXi3EjCxmrfKX6s%2FScreenshot%202024-06-20%20at%2017.22.25.png?alt=media\&token=92688bf2-f7b4-4c1c-aafb-7227f2bbfa2f)

### Manage Movements & Dashboards

Continue reading here for a guide to setting up your **Player Feature Movements** (computations). 

{% embed url="<https://www.fasttrack-solutions.com/en/resources/knowledge-base/the-singularity-model/player-features/manage-movements>" %}

Read more about **Player Feature Dashboards** here:

{% embed url="<https://www.fasttrack-solutions.com/en/resources/knowledge-base/the-singularity-model/player-features/manage-movements/player-feature-dashboard>" %}