Free guide · ChatGPT settings review
ChatGPT Settings Review Checklist
Review one category at a time before you use ChatGPT for work. The goal is not to choose the same setting as everyone else. It is to know which account you are using, what the current control does, who owns the decision and what you decided.
1. Start with the account and the work
Record the context before changing anything.
CHATGPT SETTINGS REVIEW Account or workspace: [personal / Business / Enterprise / Edu / other] Account email or label: [enough detail to identify the account — do not put a password here] Device or surface: [web / mobile / desktop] Work I expect to do: [drafting, analysis, research, files, connected apps or other] Information involved: [public / internal / confidential / restricted] Workspace owner or administrator: [name or team, if applicable] Review date: [date] Next review date: [date or trigger]
Do not paste confidential material merely to test a setting. Use a harmless sample and follow your organization’s policy.
2. Data controls
Open Settings → Data Controls and record what your account shows.
| Check | What to record |
|---|---|
| Account type | Personal account or managed workspace |
| Model-improvement control | Whether Improve the model for everyone is shown and whether it is on or off |
| Organization rule | Any workspace policy or administrator instruction that applies |
| Decision | Keep, change, or ask the workspace owner |
| Evidence | Date checked and, if allowed, a screenshot or policy reference |
For a personal account, decide whether the model-improvement setting fits the material you plan to use. Business and managed workspaces can follow different organization settings. A personal toggle is not a substitute for your employer’s information-handling rules.
3. Memory
Open the current memory or personalization controls and review what ChatGPT may retain or reference.
MEMORY DECISION Saved memories shown: [yes / no / unavailable] Reference to past chats shown: [yes / no / unavailable] Items that should remain: [list] Items to remove: [list] Reason: [why] Owner: [you / workspace administrator]
Deleting a conversation does not necessarily delete a saved memory. Treat the chat and the saved-memory controls as separate places to review. Test with a harmless question such as “What do you remember about how I prefer reports formatted?” and inspect the answer before relying on it.
4. Chat history
Use the right action for the result you want.
| Action | Use it when | Check afterward |
|---|---|---|
| Keep | The conversation is still useful and appropriate to retain | Title, project and account are correct |
| Archive | You want it out of the regular sidebar but still retained | It appears in the archive and can be restored |
| Delete | You want it removed from your account view and scheduled for deletion under the applicable policy | The conversation is gone from the active and archived views |
OpenAI’s current workspace documentation says deleted chats are generally scheduled for permanent deletion within 30 days, subject to published security, legal and de-identification exceptions. Your workspace retention policy may differ. Record the policy that applies instead of assuming that disappearing from the sidebar means every related item is gone.
5. Library and files
Review files separately from chats.
| File | Where it is saved | Still needed? | Contains sensitive material? | Action and owner |
|---|---|---|---|---|
| [file name] | [Library / project / chat / device] | [yes / no] | [yes / no] | [keep / remove / ask] |
Deleting a conversation does not delete a file saved separately in Library. Project files, Library files and transient chat uploads can follow different retention rules. Check each storage location that appears in your account.
6. Apps and connected services
Review each connection as a separate authorization decision.
CONNECTED APP REVIEW App or service: [name] Connected account: [account label] Workspace allows it: [yes / no / ask] Information it can read: [scope] Actions it can take: [read / create / update / delete / other] Confirmation setting: [what the account or workspace shows] Still needed: [yes / no] Decision and owner: [keep / restrict / disconnect / ask] Test completed with harmless data: [yes / no]
An available app does not automatically mean the correct account is connected or that every action is permitted. Check the connected account, approved scopes, workspace access and action permissions separately. Disconnecting an app stops future access through that connection; it does not automatically remove information already saved in a conversation, generated file or another record.
7. Worked example
Scenario: A manager wants to use ChatGPT to help draft an internal supplier review.
- Account: Company-managed workspace on the web.
- Data controls: The manager records the workspace policy instead of relying on a personal-account assumption.
- Memory: A harmless test shows an old formatting preference. The manager keeps the preference but removes an outdated role description from the separate memory controls.
- Chat history: A test conversation is deleted. An older useful template conversation is archived.
- Library: A downloaded supplier spreadsheet is found in Library and removed after confirming that the approved copy exists in the company system.
- Apps: The manager confirms that the connected drive uses the company account and has read-only access to the intended folder. A harmless test file is used before real work begins.
- Decision: The manager records the review date and schedules another check after a workspace-policy change or new app connection.
The useful result is the decision record—not a claim that every setting should be on or off.
8. Final review
- I confirmed the account and workspace I am using.
- I know which organization policy applies to work information.
- I recorded the current Data Controls decision.
- I reviewed saved memories separately from chat deletion.
- I used keep, archive and delete intentionally.
- I checked Library, project files and chat uploads separately.
- I verified every connected app’s account, permissions and action scope.
- I tested with harmless information before using real work material.
- I recorded the owner, evidence and review date for unresolved decisions.
- I will review again after a plan, workspace, policy or connected-app change.
Official documentation used for the review
- Use ChatGPT — feature availability depends on plan, platform, region, rollout and workspace settings.
- ChatGPT Work overview: retention by data type — conversations, Library files, project files, memories and connected-app data have separate controls.
- ChatGPT Work overview: connected applications, credentials and permissions — workspace availability, connected accounts, source-system permissions and action settings are separate decisions.