added tenant configuration

Concepts:-Multi-Tenancy.md

@@ -16,3 +16,22 @@ The feature flighting system would take care of creating and maintaining the Fla
 If there is no need for multi-tenancy and you want to use the Feature Flighting System for a single application, then you will need to board only a single tenant. However, if you want to multiple applications or downstream tenants to use the same service then a separate Admin team is needed for maintaining the deployed artifacts. The admin team will also have the added responsibility to board any downstream partners.
 
 ## Tenant Configuration
+For each tenant the following configurations are required
+| Name | Type | Description | Config Path |
+| :--- | :--- | :--- | :--- |
+| Name | String | Full name of the tenant | Name |
+| Short Name | String | Short name (moniker) of the tenant | ShortName |
+| Auth Type | String | Type of authorization allowed. Currently only 'Configuration' type is allowed | Authorization:Type |
+| Cache - Feature Flag Names | String | [Cache type](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Caching#cache-types) to cache names of Feature flags | Cache:FeatureFlagNames |
+| Cache - Feature Flags | String | [Cache type](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Caching#cache-types) to cache feature flag results | Cache:FeatureFlags |
+| Cache - Graph | String | [Cache type](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Caching#cache-types) to cache data from graph (User list from Group) | Cache:Graph |
+| Cache - Operator Mapping | String | [Cache type](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Caching#cache-types) to cache the [filter-operator mapping](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Filter-and-Operators#operator) | Cache:OperatorMapping |
+| Cache - Rules Engine | String | [Cache type](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Caching#cache-types) to cache the [Rules engine JSON](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Rules-Engine-Filter) | Cache:RulesEngine |
+| Cache - URP |  URP Config | Feature flighting system is integrated with [Unified Redis Platform](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Caching). Provide App, Cluster and Secret Location. | Cache:URP |
+| Enhancements - Disabled Context | bool | Enables or disabled the disabled context | Evaluation:AddDisabledContext |
+| Enhancements - Add Enabled Context | bool | Enables or disabled the enabled context | Evaluation:AddEnabledContext |
+| Enhancements - Ignore Exception | bool | Will evaluate the feature toggle to `false` for any unhandled exception during execution | Evaluation:IgnoreException |
+| BRE Enable | bool | Rules Engine filter is enabled when set to `true` | BusinessRuleEngine:Enabled |
+| BRE Storage Connection String Location | String | Secret key in Key Vault containing the connection string of the Storage Account having [Rule Engine JSON files](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Rules-Engine-Filter#enabling-rules-engine-filter) | BusinessRuleEngine:Storage:StorageConnectionStringKey |
+| BRE Container Name | String | Name of the blob container with the [Rule Engine JSON files](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Rules-Engine-Filter#enabling-rules-engine-filter) | BusinessRuleEngine:Storage:StorageConnectionStringKey |
+| BRE Cache Duration | Number | Duration (in mins) to cache the [Rule Engine JSON files](https://github.com/microsoft/FeatureFlightingManagement/wiki/Concepts:-Rules-Engine-Filter#enabling-rules-engine-filter) | BusinessRuleEngine:CacheDuration |