Start Here
Feature visibility and permissions
Learn why a page, record or action may appear for one office or user but not another.
Written by Katrin Erb Updated Published Flinq combines feature settings and permissions. Both must allow access before a product page or action appears.
Office feature settings
Office Settings controls whether optional products such as Interest Pooling, Standing Rates, management-account reconciliation, Books and Fixed Term Deposits are enabled. Some child settings appear only after their parent feature is enabled.
User permissions
Roles are assigned in the current office. A role grants permission categories such as viewing the dashboard, importing statements, managing pools, creating payment runs or administering users. Custom roles can provide a narrower set of permissions.
Record context
Some actions also depend on the selected record. For example, an account must match a pool's bank, currency and branch; an automated importer must be configured before it can be activated; and completed financial periods cannot be rewritten.
If something is missing
-
Confirm that you are in the correct office.
-
Ask an Office or Organisation admin to review the office's feature settings.
-
Ask them to review your roles in that office.
-
Check whether the record meets the action's eligibility or workflow requirements.
Keep reading