dosubot[bot] commented on issue #30678: URL: https://github.com/apache/superset/issues/30678#issuecomment-2430260616
<!-- Answer --> If the "pgsql" schema is not visible in the permissions list while other schemas are, it might be due to specific conditions or configurations affecting its visibility. Here are a few things to check: 1. **Schema Permissions**: Ensure that the "pgsql" schema has the correct permissions set in Superset. You can verify this by checking the role permissions in the Superset UI under `Security` > `List Roles`. Make sure the role associated with the user has the `[database].[schema]` permission for "pgsql". 2. **Security Manager Configuration**: Superset's security manager uses the `get_schemas_accessible_by_user` method to determine schema visibility based on user permissions. If the "pgsql" schema is not included in the user's permissions, it will not be displayed <sup>[[1]](https://github.com/apache/superset/blob/master/superset/security/manager.py)</sup>. 3. **Default Catalog**: If the schema is associated with a non-default catalog, it might be excluded from the permissions list. The logic in the `downgrade_schema_perms` function indicates that schemas not associated with the default catalog may have their permissions deleted <sup>[[2]](https://github.com/apache/superset/blob/master/superset/migrations/shared/catalogs.py)</sup>. 4. **Configuration Settings**: Check if there are any specific configurations or settings in Superset that might affect schema visibility. This includes ensuring that the security configurations are correctly set up to allow access to the "pgsql" schema <sup>[[3]](https://github.com/apache/superset/blob/master/superset/commands/database/importers/v1/utils.py)</sup>. By reviewing these areas, you should be able to identify why the "pgsql" schema is not appearing in the permissions list and make the necessary adjustments. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
