Support
Four channels, and it matters which one you use — particularly the third.
How do I do X? Is my setup safe?
Public, searchable, and the answer helps whoever hits the same thing next. This is the fastest route for anything about using the library.
Discussions →Something is broken, or behaves differently to the docs
Include your tenantlayer.* configuration and the role your application connects as — those two answer most reports immediately.
Issues →One tenant can read another tenant's data
Never in a public issue, and never by email. That form is visible only to the maintainers. Acknowledgement within 3 working days.
Private security advisory →Commercial licensing, or help with a migration
Anything that does not belong in public.
Contact form →
What support currently is
TenantLayer is Apache 2.0, and support for it is GitHub Issues and Discussions — answered as fast as is honestly possible, which is usually quickly, and is not a service level agreement.
There is no support email, and that is deliberate rather than an oversight. An address implies a guaranteed response time, and a promise broken is worse than one never made. Priority email support arrives with the paid tier, when it is something you are paying for and something that can be committed to.
Security reports are the exception. Those are triaged ahead of everything else, whether or not you are a customer.
Before you ask
Two answers cover most questions. Are you connecting to Postgres as a superuser or the table owner? Both bypass row-level security by design. Is the data coming from a cache? A cache hit never reaches the database, so no policy can help. Both are covered in troubleshooting.