Resources
Learn, get support, and find the right Niatse path.
Resources are organized around learning, support, and contact so operators, partners, and teams can find help without navigating the authenticated app.
Learn
Public education for operators, partners, and ecosystem builders.
Blog, guides, case studies, press, and changelog stay as public content routes
Articles should avoid accounting jargon unless they define it clearly
Every education surface should help users feel more in control
Support
Help and documentation paths for users who need answers before or after sign-in.
Docs and help stay separate from internal workspace guidance
Support plans can be introduced here before becoming a full commercial surface
Professional services remain a consultative path, not a forced upgrade
Managed support plans
A future route for structured implementation, migration, and operator success support.
Use this anchor until support plans become a full page
Keep expectations practical and non-hype
Connect to contact sales for high-touch requests
Professional services
A consultative path for businesses and institutions that need setup, migration, workflow design, or partner rollout help.
Migration support should preserve data review and approval
Enterprise support should not bypass workspace permissions
Partner programs need scoped implementation plans
Contact
Sales, partner, enterprise, support, privacy, press, legal, and security requests should route to the right contact path.
Contact sales uses a clear intent query
Partner and enterprise paths stay public
Sensitive requests should use the existing contact and security channels