mirror of https://github.com/docusealco/docuseal
master
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.0.8
1.1.0
1.1.1
1.1.10
1.1.11
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.1.9
1.2.0
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.4.0
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
1.5.7
1.5.8
1.5.9
1.6.0
1.6.1
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
1.7.0
1.7.1
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.7
1.7.8
1.7.9
1.8.0
1.8.1
1.8.2
1.8.3
1.8.4
1.8.5
1.8.6
1.8.7
1.8.8
1.8.9
1.9.0
1.9.1
1.9.10
1.9.2
1.9.3
1.9.4
1.9.5
1.9.6
1.9.7
1.9.8
1.9.9
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
2.0.6
2.0.7
2.0.8
2.0.9
2.1.0
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.2.0
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9
2.3.0
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.4.0
${ noResults }
4 Commits (b7800246f94dd62e9be433e5bb73bb6ff5a06a1e)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Ryan Arakawa
|
001df1367e
|
CP-11557 user account scoping (#38)
* Scope email and external_user_id uniqueness to account Allow the same email and external_user_id to exist across different accounts while maintaining uniqueness within each account. Changes: - Scope external_user_id uniqueness to account_id - Scope email uniqueness to account_id - Remove Devise :validatable to avoid global email uniqueness - Update ExternalAuthService to use account-scoped queries - Update TokenRefreshService to use account-scoped queries - Add custom email validation with account scope * Add and update tests for account-scoped user uniqueness * Run migrations and update schema * Document account-scoped user lookup behavior * skip password test * we use access token validation via iframe, not passwords so this test is not necessary. * update test for rubocop |
4 months ago |
|
Ryan Arakawa
|
741c548d26
|
CP-11042 partnership features updated (#26)
* Add partnership template authorization and ability system * Update template authorization to support partnership context * Add request context-based authorization for API access * Implement hybrid partnership/account authorization logic * Add submission authorization conditions for partnerships * Support global partnership template access * Add template cloning services for partnership workflows * Update template cloning to require explicit target parameters, to allow for cloning for either account or from partnership * Add Templates::CloneToAccount service for partnership to account cloning * Add Templates::CloneToPartnership service for global to partnership cloning * Add logic to detect account vs partnership template cloning with validation * Add folder assignment logic for cloned templates * Add external authentication and partnership support * Update ExternalAuthService to support partnership OR account authentication * Implement user assignment to accounts when partnership context is provided * Support pure partnership authentication without account assignment * Update API controllers for partnership template support * Add partnership request context to API base controller * Update submissions controller to support partnership templates * Add partnership template cloning to templates clone controller * Refactor template controller webhook logic to reduce complexity * Support external_account_id parameter for partnership workflows * Update web controllers and views for partnership template support * Add tests * erb_lint fixes * add local claude file * shared concern for handling partnership context * remove overly permissive case * global templates should be available for partnerships and accounts * pass through access context in vue * add tests * add partnership context and tests to submissions * add token refresh as last resort for a corrupted token |
5 months ago |
|
Ryan Arakawa
|
7d592d4761
|
CP-11138 partnership refactor (#22)
* account group to partnership rename * this is mostly converting the name account_group => partnership * partnership user relationships are API request based * so we don't need to maintain relational information in two databases, this many to many relationship is now handled via API context * rubocop and test fixes |
6 months ago |
|
Ryan Arakawa
|
a1ed992ee4
|
CP-10294 add account groups (#19)
- Add account_groups table and model - Add account_group references to accounts, users, templates, template_folders - Make account_id nullable on users, templates, template_folders - Add controllers and specs * Consolidate account groups migrations - Replace 8 separate migrations with 2 consolidated ones - Create account groups and relationships in one migration - Make account_id columns nullable in second migration * this logic is being handled in external_auth_controller * remove unnecessary controllers * remove unnecessary routes * refactor account_group.default_template_folder * align method with Account version of this method * refactor controllers to move complex logic to service * move account/account group validation to concern * this method is not yet needed * we may implement this differently in next ticket to handle account and account group syncing for templates. * rubocop violation fixes * a few more refactors and add tests * Change external_account_group_id to integer type * Refactored external_account_group_id from string to integer in models, migrations, factories, and specs for consistency. * Merged account_id nullability changes into a single migration and removed the obsolete migrations. * Updated authentication logic to require either account or account_group presence for user activation. |
6 months ago |