[feature]: Allow non-admin users to access import settings

[deeonwuli]

📌 References

• Issue: Closes https://app.clickup.com/t/869dn72ua

📝 Implementation

Adds a new importSettingsAccess permission field to AppSettings (stored in the user-extended-app-settings constant). Non-admin users listed in this field can open the settings dialog and see only the Import tab, without access to the rest of the settings.

• New CheckCurrentUserCanAccessImportSettingsUseCase checks: super admin, full settings access, or import-only access
• Settings gear icon is shown if the user qualifies for either access level
• Admin can configure import access via Settings → Permissions → "Access to Import Settings"

📹 Screenshots/Screen capture

🔥 Testing

1. As admin, go to Settings → Permissions → enable "Access to Import Settings" and add a user/group
2. Log in as that user — gear icon is visible, clicking it shows only the Import tab
3. A user in neither list sees no gear icon

#869dn72ua

[bundlemon]

BundleMon

No change in files bundle size

Groups updated (1)

Status	Path	Size	Limits
✅	Build Folder ./**/*	1.41MB (+851B +0.06%)	+20%

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[eperedo]

can we remove the fuzzy translations? Here, but also for PT and PT_BR

[eperedo]

I'm not sure about this change. This means that users who have access to the import action can now open the 'settings' modal and configure any permission. This was not part of the task, so maybe we should stick to the previous logic?

[eperedo]

The whole usecase is ok, but this is almost the same logic we have in CheckCurrentUserCanAccessSettingsUseCase.ts. I think we can have only one usecase and instead returning a boolean we can return a new type:

type UserSettingsAccess = {
  accessToSettings: boolean;
  accessToImport: boolean;
}

and now we can centralize every access logic in this usecase so in the future we don't need one usecase for every new setting and also we save hitting the server with the same two requests to get the current user and the appsettings. Does this make sense? What do you think?