Configure Account Setting

These settings help define how your organization uses the system. They may affect account identity, available features, setup behavior, workflows, integrations, and how users experience the platform.

Because account settings can affect several areas of the system, they should be reviewed early during implementation and again before going live.

What account settings are used for

Account settings are used to configure organization-level behavior.

Depending on your account setup, account settings may include:

Organization details
Account-level configuration
Enabled features or modules
Setup mode options
Integration-related settings
Display or branding options
Operational preferences
Settings that affect workflows across the account

The exact options available may depend on your account, enabled features, and your permissions.

Why account settings matter

Account settings are not only administrative details. They can affect how the rest of FlightLogger Maintenance works.

For example, account-level setup can influence:

Which features are available
Which setup tools are visible
How users access the system
How imports and onboarding are handled
How integrations are configured
How operational workflows behave
How account-specific terminology or templates are used

This is why account settings should be controlled by users who understand both the system and the organization’s maintenance process.

When to review account settings

You should review account settings:

When setting up FlightLogger Maintenance for the first time
Before inviting a large number of users
Before importing data
Before connecting FlightLogger
Before going live
When your organization changes operational procedures
When new features or modules are enabled
When troubleshooting account-wide behavior

It is usually better to confirm core settings before adding large amounts of operational data.

Who should manage account settings

Account settings should normally be managed by account administrators or implementation users with the correct permissions.

Avoid giving broad account configuration access to users who only need to perform daily operational work.

For example:

A technician may need access to active work orders, but not account settings.
A purchasing user may need access to suppliers and purchase orders, but not integration configuration.
A planner may need access to aircraft and work orders, but not all account-level setup.

Keeping account settings restricted helps protect the consistency of the system.

How to access account settings

To review or update account settings:

Go to Initial Setup.
Open Account Settings.
Review the available configuration options.
Update the required settings.
Save your changes.
Review any affected workflows if the change impacts operational behavior.

If you cannot see Account Settings, your user may not have the required permissions.

What to check during implementation

During implementation, review account settings together with your onboarding plan.

Important questions include:

Is the organization name correct?
Are the required features enabled?
Is setup mode needed for import or migration?
Are the correct users responsible for account administration?
Are integrations required?
Are templates or account-specific documents needed?
Are purchasing and currency settings required?
Are user roles and permissions ready to be configured?
Are any settings likely to affect go-live?

These questions help prevent rework later.

Setup mode

Some onboarding or import features may only be available when setup mode is enabled.

Setup mode is typically used during initial configuration, migration, or data import. It should be handled carefully because it may expose setup tools that are not part of normal daily operation.

If your account uses setup mode, confirm:

Who should have access to setup tools
Which imports need to be completed
When setup mode should be disabled
Whether imported data has been validated

Account settings and integrations

Some integration setup is managed from Administration or Initial Setup areas, while detailed integration guidance belongs in the Connect FlightLogger section of the Help Center.

If your organization connects FlightLogger and FlightLogger Maintenance, account administrators should confirm:

Whether FlightLogger Sync is required
Whether OAuth applications are required
Which aircraft or aircraft models should be synchronized
Who is responsible for monitoring sync issues
Whether hours, cycles, and defects are expected to sync

Do not assume integration behavior is active until the relevant setup has been configured and verified.

Account settings and permissions

Account settings and permissions are closely related.

A user may be able to see or change account settings only if their role and permissions allow it.

If a user cannot access Account Settings, review:

The user’s role
The permissions included in that role
Whether the user should have account administration access
Whether the user is working in the correct account

Account settings should not be used as a workaround for incorrect role design. If access is wrong, update the user’s role or permissions.

Best practices

Review account settings before go-live.
Limit account settings access to trusted administrators.
Document important configuration decisions.
Avoid frequent changes to core settings after users begin daily operations.
Review settings after major process changes.
Check account settings before troubleshooting account-wide behavior.
Confirm integration settings before expecting synced data.
Make sure setup mode is only used when needed.

Summary

Account settings define important account-level behavior in FlightLogger Maintenance.

They help align the system with your organization, your onboarding plan, your users, your integrations, and your operational workflows.

A careful account settings review early in implementation makes the rest of the setup easier and helps reduce confusion when daily maintenance work begins.