# Company Settings
Flylogs allows you to customize how your data is managed and what limits you want to enforce within your organization.
**Among the all the options, you can:**
* enable and disable Flylogs features,
* manage flight permissions for each user type,
* block logbook changes in the past,
* change flight document retention policies and
* customize pilot duty time limitations.
You can customize all this settings from your Company Settings page.
Edit flight data modification permissions for each user type.
You can customize which profiles can create flights, confirm them or edit and delete them once they are on the logbooks.
Additionally, to enhance the security in shared office computers, the last checkbox "**Require user Password to confirm flights into logbooks**" enables a second validation step by asking for the user´s password in order to confirm the flights.
### Flight permissions
Flylogs splits flight handling into three independent permissions. For each one, you decide which user types in your company are allowed to perform the action:
* **Create flights** — draft a new flight from the Flights page or dispatch a scheduled flight into a draft.
* **Confirm flights** — turn a completed draft into a confirmed entry in the logbooks.
* **Edit & delete flights** — change values on a confirmed flight or mark it as deleted.
Each permission is granted per user type (Pilot, Captain, Flight Instructor, Chief Pilot, Flight Dispatcher, etc.). A user only sees the matching button once their user type is enabled in the corresponding list.
#### What happens when a permission is missing
| Action | Where the button appears | If your user type is not allowed |
| --------------- | ------------------------------------ | --------------------------------------------- |
| Create flight | Flights page, top-right "Log flight" | Button is hidden |
| Dispatch flight | Schedule modal, "Dispatch flight" | Action is hidden in the dropdown |
| Confirm flight | Flight view, green confirm button | Button is hidden |
| Edit flight | Flight view, edit button | Button is hidden |
| Delete flight | Flight view, delete button | Button is hidden |
| Cancel flight | Flight view, cancel button | Visible only to the crew of an upcoming draft |
#### Rules that always apply
* **Company Administrators and Operations Managers** can create, confirm, edit, delete and cancel any flight regardless of how the permissions are configured. These two roles are never restricted.
* **Creator and PIC self-edit window** — the user who created the flight, or the pilot listed as PIC, can always edit a confirmed flight for **24 hours** after it was last modified, even if their user type is not in the edit list.
* **Active pilots only** — to create a flight you must be marked as a pilot in your profile and your account must be active. A staff-only user (no pilot flag) above the Crew Scheduling level cannot create flights even if their user type is allowed.
* **Historical and deleted flights** are locked for everybody — no edits, no deletes, no confirmations.
Permission changes take effect immediately for every user, on their next page load. There is no need to log out and back in.
### Pilot flight duty time limitations
Flylogs can be a great help to track flight time and duty time limitations.
Flylogs scheduling tool will alert your roster manager when creating the flight schedule if any slot does not comply with your legal requirements.
On top of that, our servers run daily background checks on all the flight time stored in our database and triggers alarms if any of your setup limits are reached.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.flylogs.com/fcom/company-management/company-settings.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.