You can then use the inherited configurations of the level above or override the inherited configurations. As we discussed, Latchel has 3 tiers- Property Level configurations will always override Portfolio Level & Company Level configurations. Portfolio Level configurations will always override the Company Level configurations. Please see the diagram below to learn about these inheritance rules (Budget Limits were used as an example):

​
Service Provider Inheritance

Service Provider inheritance is a special case. When you turn Service Provider inheritance ON, you have the option to ADD Service Providers to the top of your preferred Service Provider list AND inherit the parent level.
  • For example, if you create a portfolio, this portfolio can inherit the Service Provider rules from the company AND add a few Service Providers on top to be called first. The Service Providers added to the portfolio take precedence over the inherited Service Providers from the company level.
You can choose to override inheritance (e.g. don’t inherit at all) and turn this feature OFF for your portfolio and/or property.
  • This means we will only look to dispatch Service Providers that are prioritized for that portfolio or property. We will NOT look at parent-level Service Provider prioritization.
You can also “copy” the parent-level preferred Service Provider list to re-arrange priorities entirely.
Copying the parent-level preferred service provider list will override the inheritance and makes it easier to start with pre-existing list.
The “copy” must be maintained separately from the company or portfolio levels. You will have 2 independent lists to manage. Preferences updates and the level that was copied will NOT transfer to the level that received the copied priorities.
Here’s an example of how a service provider could possibly work on a job order for a certain property depending on the inheritance set for the service provider.
The below diagram describes how configuration inheritance affects the emergency escalation contacts.