Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(analytics): refactor and introduce analytics APIs to accomodate OrgLevel, MerchantLevel and ProfileLevel authentication #5728

Closed
tsdk02 opened this issue Aug 28, 2024 · 0 comments · Fixed by #5729, #5784 or #5811
Assignees
Labels
A-Analytics C-feature Category: Feature request or enhancement

Comments

@tsdk02
Copy link
Contributor

tsdk02 commented Aug 28, 2024

Currently, we are using only MerchantID for obtaining the analytics through metrics and filters.

We are now introducing OrgLevel, MerchantLevel and ProfileLevel authentication for analytics, so we need to do the following:

  • refactor the existing MerchantLevel APIs
  • introduce new OrgLevel APIs
  • introduce new ProfileLevel APIs

The levels are described as:

    OrgLevel {
        org_id: id_type::OrganizationId,
    },
    MerchantLevel {
        org_id: id_type::OrganizationId,
        merchant_ids: Vec<id_type::MerchantId>,
    },
    ProfileLevel {
        org_id: id_type::OrganizationId,
        merchant_id: id_type::MerchantId,
        profile_ids: Vec<id_type::ProfileId>,
    }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment