Skip to main content

Users, organization and subscription

When to use​

Use this page to check the active organization, manage Users, and understand Subscription, Plan, Usage, and Invoices.

Pre-conditions​

  • Logged in.
  • Administrative permission in the organization.
  • Sandbox environment for signup and billing tests.

Sample data used​

  • Organization: authorized sandbox.
  • Fictitious user: usuario.demo@plantaro.example.

Step by step​

Active organization​

  1. After login, check the organization selector in the authenticated layout.
  2. Select the correct organization.
  3. Verify that the URL uses the same organizationId.

Expected result: all modules display data from the selected organization.

Organization and properties​

  1. Go to /:organizationId/organization.
  2. Check registration data, properties, or visible settings.
  3. Edit only data authorized for the sandbox organization.

Organization data

Expected result: administrative information reflects the active organization.

Users​

  1. Go to /:organizationId/users/list.
  2. To create a user, go to /:organizationId/users/new.
  3. To edit, go to /:organizationId/users/edit/:id.
  4. To change your own password, go to /:organizationId/users/change-password.

User list

Expected result: authorized users can be listed, created, edited, and have their password changed according to permission.

Subscription and Plan​

  1. Go to /:organizationId/billing.
  2. Check the Subscription overview.

Subscription overview

  1. Go to /:organizationId/billing/plans to compare Plans.
  2. Go to /:organizationId/billing/usage to check Usage and limits.
  3. Go to /:organizationId/billing/invoices to check Invoices.

Expected result: the user understands which limits affect the creation of areas, beds, resources, crops, and plans.

Payment, success and cancellation​

  1. Use /:organizationId/billing/payment-processing only in a secure environment.
  2. Do not trigger a real charge during documentation.
  3. Consult return routes only when generated by the test flow: subscription-success, subscription-cancel, upgrade-success, and upgrade-cancel.

Expected result: payment states are documented without triggering a real charge.

Errors and empty states​

  • No permission for Users: request an administrative profile.
  • Plan limit reached: review Usage and upgrade the plan if necessary.
  • Empty invoices: may indicate an organization without a billing cycle in the sandbox.