Skip to content

Can a subscription be attached to a model other than User? #491

@scottward

Description

@scottward

Our app enables multiple users to be a part of a single organization. We'd like to use Pay to set up a organization.subscription with different quantities depending on how many users they add.

It looks like the standard approach is user.subscription, but that isn't quite right in this case.

How can we associate a subscription with Organization instead of User?

Or, am I missing an easy workaround? What's the best practice in this case?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions