Hello,
I understand the designed behavior for login is to consider if the member has any open invoices and, if so, redirect to /Sys/Profile/Finances (as documented at https://gethelp.wildapricot.com/en/articles/190).

This approach to onboarding new members goes against the spirit of our organization. To explain, our members are school district employees - often several people from the same district - and tend to be consistent year-to-year. Their fees are paid by their employers (by check) once we send them an invoice, but in the mean-time, they should be permitted to freely browse the members-only portion of the website without the redirect.

Would you consider some sort of "Override redirect to Finances on login" option as part of the "Starting Page" configuration?

In the mean-time, I have found a solution. If the querystring parameter of "ReturnUrl=" is provided on /Sys/Login, the redirect to Finances will not occur.

So, I manipulate the login link with javascript like the following:

```
var loginLinks = document.getElementsByClassName("loginLink");
for(var i=0;i<loginLinks.length;i++){

if(typeof loginLinks[i] === "object" && loginLinks[i].tagName === "A" && !loginLinks[i].search.match(/returnurl=/i)){

    var u = new URL(loginLinks[i].href);

    u.search += (u.search.indexOf("?") !== 0 ? "?":"&") + "ReturnUrl=%2f";

    loginLinks[i].href = u.href;

}

}
```

PLEASE, PLEASE, PLEASE, PLEASE, use a consistent and different term for the overall WA account primary admin person vs. a bundle membership account admin person vs. one of the people authorized to work in the WA modules.

I sent out invoices to the entire membership last night and checked the box to send a copy to the organization contact, which is me (membership-dues@idesst.org). That did happen, but a copy of every invoice ALSO went to our president who has full WA access and is one of the 5 administrators, but is not the primary organization contact!!

The term administrator seems like it gets used inconsistently to mean both, which is extremely confusing. There needs to be consistent, and separate terms for 3 different types of users: primary organization contact, a WA admin, and a bundle admin. Frankly, the way the word "bundle" is used on your site is not a common usage here in the US. We would more likely use family membership or group membership, or maybe make that a customizable item when the primary organization contact sets up WA. I have attached examples of the confusion... Thanks, Diane

For example ...

In various operations, the HTML view is mushed together unless we first add an innocuous space (or something), save and reopen. How long would it take to fix that bug?

In the opt-out macro, the only acceptable syntax is {Unsubscribe_Url}, exactly like that. Anything else (e.g., "URL" or a space instead of an underscore), and the link won't work. Worse, your system will put an unsightly "HEY CLICK ME" invitation to opt-out at the email's bottom. How long would it take to correct your examples (and make their syntax uniform) and make the macro case-insensitive? (I suggest also accepting either a space or an underscore, as various macros have both forms, and you'll need to make them backwards-compatible.)

I could round up more examples, but surely Support has a list. I'd think fixing such glitches would save us all (including Support) a lot of time, as well as improve usability, user confidence, and even moral.

Rather than worry about specific, discrete pieces of functionality, I'd propose an overhaul of the entire user experience including:
1) Make reports that are more useful, e.g. new members, lapsed members, invomplete registrations
2) Overhaul the email workflwo, e.g. you should be able to name an email before step three in the process
3) A complete overhaul of the event setup and pricing elements. e.g. Having to create a registration form is a nightmare. Why aren't there simple templates and an ability to preview a form without having to log in as a user?

With all due thanks, and respect, pleasing the 5% of power users who are asking (demanding) specific pieces of functionality is a waste of time when 90% of the users can't get through the basics because an overall design and UI that are clearly from the late 1990's early 2000's.

I hope the above is both constructive and helpful. I do appreciate the work that goes into WA, and offer it to help. Kind regards--Jim