Consider creating Postgres schema with broader permissions

[dr-rodriguez]

When using Felis to create a Postgres database, the schema it creates is private to the user that ran the code. For testing that has been fine, but we realized that sharing this between users means that if one of us created the database in a shared server, the other users doesn't have access to the schema and tables when they should.

This was easily fixed with something along the lines of:

GRANT USAGE ON SCHEMA "exomast" TO PUBLIC;
GRANT USAGE ON SCHEMA "TAP_SCHEMA" TO PUBLIC;

Could this be something to consider when preparing database via Felis?
Or is the intent that things like this be left to database administrators after the fact?

I can certainly see cases where one would want to restrict access, but expect the default scenario would be making it more public.