Feature visibility and permissions

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.

Managed-entity and team access

Some offices restrict client or managed-entity records to assigned users and, where enabled, teams. A role grants the action permission, while the user or team assignment determines which eligible records are in scope. If you can open a product area but cannot find an expected client record, ask an administrator to check both your role and the record assignment.

Pilot or deployment-gated features may also require an environment setting or office allow-list. A permission alone does not make those features available.

If something is missing

1. Confirm that you are in the correct office.

2. Ask an Office or Organisation admin to review the office's feature settings.

3. Ask them to review your roles in that office.

4. Check whether the record meets the action's eligibility or workflow requirements.