Skip to content

Conversation

@Nadil-K
Copy link
Member

@Nadil-K Nadil-K commented Feb 2, 2026

Migration Checklist

  • Find all the tables that have hyvor_user_id and add a new nullable int organization_id column to it
  • env changes
    • Add DEPLOYMENT env variable.
    • Remove AUTH_METHOD
    • Change HYVOR_PRIVATE_INSTANCE to http://hyvor.internal
  • CloudContext must be used. Org switch must be handled
  • Resource creation must be updated to use ResourceCreator HDS component
  • AuthInterface now have me() instead of check(). It returns user and organization both in an object.
  • Init calls in the Console must be updated to get the correct data needed for CloudContext
  • Resources comms
    • ResourceCreated event when created
  • adding members
    • change all "owners" to "admins", who have full access to the resource #462
    • update UI to use OrganizationMembersSearch
    • update API endpoint
      • to verify that the given user is part of the organization
      • to directly add the user to the resource
      • remove user inviting logic
  • Create the migration command (see below)
  • Send emails to first admin
  • Billing section
    • Org role-based access
      • Disable button
      • Redirect on URL access
    • Usage updates
  • Comms Events
    • MemberRemoved (remove the user from all resources of the organization)
    • UserDeleted (remove the user from all the resources)
    • LicenseChanged (optional, clear cache or something)
  • Console Authorization Updates
    • Must check that the current resource's organization = user's current organization
    • Also check that the user's current organization as seen by the frontend, is the same in the backend. In case of a mismatch, fully redirect the user (location.href) to /console
  • Design lib has to be updated 2.0.3
  • Manual testing (test with a newly signed up user, not the seeded one):
    • creating a new resource when there is no active organization
    • creating a new organization from the bar
    • switching between organizations while in the console
      • at /new
      • at /console
      • at /console/{resource}
    • cannot access resources of other organizations (redirects to /console)

Copy link
Member

@supun-io supun-io left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Rename UserLevelEndpoint to OrganizationLevelEndpoint
  • send X-Organization-Id from the frontend for those routes and the ConsoleAuthorization listener should verify the user's current organization = the organization sent from the frontend

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants