Payroll user invitation #55
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rockstardev
requested changes
Jan 25, 2025
There was a problem hiding this comment.
Rebase this branch on top of the latest master and add a bool EmailInviteForUsers setting to the configuration. Provide customization options for the email subject and body, similar to how it’s done for bool EmailOnInvoicePaid.
If this new setting is enabled, add a toggle during user creation labeled "Send Email Invite to User."
-
If the toggle is enabled:
- Hide the password fields.
- Display the Email Subject and Body fields (pre-filled with default values).
- Trigger the new email invitation flow.
-
If the toggle is disabled, use the existing flow.
Default Email Subject:
You are invited to create a Vendor Pay account
Default Email Body:
Hello {Name},
You are invited to create an account on {StoreName}'s Vendor Pay portal by visiting the following link:
{VendorPayRegisterLink}
Once your account is created and you log in, you will be able to:
- View your invoices and submit new ones.
- Click 'Upload Invoice' to add a payable invoice. Fill out the information accurately. By using the Vendor Pay portal, you are solely responsible for providing an accurate Bitcoin address and assume all liability for any incorrect or inaccessible address.
- Describe what the payment is related to; be as descriptive as possible to avoid delays.
- Upload the corresponding invoice file.
Payments will be issued in accordance with the terms of the contracted payment and purchase order.
If you have any questions, please reach out to XXXXXX.
Thank you,
{StoreName}
|
@TChukwuleta are you still working on this? |
|
Yes... I would pick this up later today. Was trying to figure something on Ghost plugin. WOuld be back here later today |
Copying of Nuget dependencies into RockstarStrikeUtils plugin Displaying payment methods in Strike plugin Exposing Strike Payment Method Id in settings for Bitcoin Stacker Automatic setting of Payment Method Id Hidding api keys in view by default Small improvements and comments Automated copying of Stripe dlls Bumping plugin for publish Updating Stripe plugin bump Listing of Exchage Order Logs Adding Delay functionality and cleaning up bugs Logging events on ExchangeOrderHeartbeatService Bumping versions of plugins Changing where condition, adding logging, bumping plugin version Executing exchange immediatelly after deposit Adding Forcing of Conversion Allowing currency conversion for all orders other than completed Bump Bitcoin Stacker version Completed state and bump Providing option to immediatelly execute heartbeat service Dealing with little tricks of Strike API Adding Deposits functionality to Strike plugin Linking deposit creation from payment methods page Bumping plugin versions Adding storeId parameter where it's missing Tweaks and optimizations Bump versions Email Notification for Paid Invoices Adding PaidAt property to Invoice Small tweaks and adding VendorPayPublicLink Unifying variables naming Depending on Store email settings not on Server email settings Depending on store email settings Improving display of invoices list Bumping plugin version Checking email settings in backwards compatible way Bump version Extracting routes root to controller Adding configuration of order delay Providing 365 day fallback as default Composite key on settings table Fixing bugs with controller redirections Add paid date to Payroll Plugin CSV Reports handle missing store in mass action route Code review changes Resetting back to BTCPay 2.0 tag Add count of users to header of Vendor Pay Users page Resetting back to BTCPay 2.0 tag Bumping Payroll and Bitcoin Stacker plugins Adding state switch for ExchangeOrders Bumping Bitcoin Stacker to 0.0.10 for publish and deploy Preserving BTC and USD balances in database Updating balance cache when execution is forced Using FetchSetting method to simplify and maintain references Refactoring method name for easier access Bumping Bitcoin Stacker plugin Fixing error with Setting reference Using both server and store email settings when sending emails Allowing manual sending of email notifications Bump versions Fixing problem with loading email settings Reformatting code per Rider settings Updating README on BitcoinStacker Payroll user invitation Update user invitation flow with feedback Payroll user invitation
|
Hello @rockstardev I have rebased and squashed commits. I have also made the requested changes, could you give it another try? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, to create a user, you need to input the password of the user.
This PR covers a user-invite flow.
As long as SMTP is configured on server settings, all the admin needs to input is a name and an email and an invite would be sent to the user, which lasts for 7 days.
The user state remains pending till the user confirms registration by setting password