Date   

Re: Owner manual "10.11.2 Editing members’ email addresses"

 

Ronaldo,

I also think this behaviour should be modified/enhanced but this is the docs group, we should discuss this in GMF or beta instead.

Cheers,
Christos


On 2020-09-29 11:47, ro-esp via groups.io wrote:
On Wed, Sep 23, 2020 at 09:51 PM, Christos G. Psarras wrote:


"if a mod changes the email address in a group, 
the change affects all groups that member is subscribed to"
EXCUSE ME ?!

That simply should not happen. It shouldn't be up to the moderator of one group to decide at which email-address a member/subscriber receives messages of another group. If this is the way it is, it should be changed.


                                               groetjes/ĝis, Ronaldo




Minor error in docs

Bruce Bowman
 

Nina -- In the downgrade section of the Owners manual, it says to go to Admin>Upgrade. If you already have a Premium or Enterprise group, the path is actually Admin>Billing.

https://groups.io/helpcenter/ownersmanual/1/upgrading-or-downgrading-groups/downgrading-a-premium-or-enterprise-group 

Regards,
Bruce


Re: Minor error in docs

Nina E
 

Good catch, Bruce. I’ll correct it in the next update of the manual.

 

Thanks!

 

- Nina

 

From: docs@beta.groups.io <docs@beta.groups.io> On Behalf Of Bruce Bowman
Sent: Thursday, October 1, 2020 1:25 PM
To: docs@beta.groups.io
Subject: [docs] Minor error in docs

 

Nina -- In the downgrade section of the Owners manual, it says to go to Admin>Upgrade. If you already have a Premium or Enterprise group, the path is actually Admin>Billing.

https://groups.io/helpcenter/ownersmanual/1/upgrading-or-downgrading-groups/downgrading-a-premium-or-enterprise-group 

Regards,
Bruce


Additional Owners Manual Suggestions

Duane
 

Owners Manual Suggestions - 9 October 2020

PDF references

2 item 9
Add Note:  If the group name chosen is in use, you will get an error saying "not available".  If there's a problem, such as illegal characters, it will say "invalid name".

3.5.3
In the Note, change to "...moderator approval unless the hashtag is modified to be Moderated.)"

3.6.13
first Note bullet change to "...is not accessible in new Basic groups (those..."

Thanks,
Duane


Re: Additional Owners Manual Suggestions

Duane
 

In 14.1, a note should be made that a hashtag, after the #, cannot be only numbers, though it may contain them. (or Mark needs to fix it ;>)

Duane


Members Manual suggestion

Duane
 

PDF 28 September 2020

7.7
There is no explanation of finding messages by number.  Suggested 7.7.5:
Change from Topic to Messages (or Expanded) view, then put the message number in the little box at the top toward the right side, hit enter.  If the message doesn't happen to be at a page dividing line, it won't be at the top of the results page.  You'll need to scroll down until you see the message with the blue bar on the left (there's no indicator on the Expanded page, so you'll need to remember which number you looked for.)


error in documentation

Henry Schaffer <hes@...>
 

At

[emailname]@[domain.com]  

<Member Name> [emailname]@[domain.com]


For the second one shouldn't it be the email address in angle brackets?


On the Invite page it says

But on the invite page is says

Emails can be of the form:


email@...

Name <email@...>


and that one with the email address in angle brackets does work and is consistent with other addressing practices.


--henry





Re: error in documentation

 

Henry wrote:

At
https://groups.io/helpcenter/ownersmanual/1/inviting-people-to-join-a-group
...
For the second one shouldn't it be the email address in angle
brackets?
Correct.

In addition, I'd strongly recommend not using [square brackets] to delimit substitution parts, as a novice may easily confuse them for part of the required syntax.

Let the words stand for themselves.

Also, the accepted form for an example domain is example.com - it is reserved so that it will never resolve to anywhere unfortunate. Using domain.com is a mistake as that is a company's actual domain name (which, appropriately enough, hosts a whois lookup).
https://en.wikipedia.org/wiki/Example.com

In this context, I don't think it is helpful to separate the invitee's email address into username and domain parts - it would be clearer to leave it together as an email address, even though the @ is a syntax part (so is the "." for that matter).

Possibly the note could also say something about substituting the invitee's actual information for "Member Name" and "username@example.com" - but that may be unnecessary clutter.

Shal


Populating Display Name

Bruce Bowman
 

Nina -- Display Name discussion is kinda scattered throughout the help. This leaves some folks unclear on how this field is populated. In particular, there is no mention anywhere that this field can be auto-populated based on content of an incoming message header.  See https://groups.io/g/Group_Help/message/1432 

Regards,
Bruce


Re: Additional Owners Manual Suggestions

Duane
 

Found an error in 10.2 (thanks to someone trying to follow the instructions ;>)  The 4 step process doesn't work as the "Send Confirmation Email" is not an option in the Actions menu.  Only the alternate method shown in the Tip is available.

Duane


Re: Additional Owners Manual Suggestions

Bruce Bowman
 

On Wed, Oct 28, 2020 at 08:33 PM, Duane wrote:
The 4 step process doesn't work as the "Send Confirmation Email" is not an option in the Actions menu.
Good catch, Duane (and Josh). I thought this was the actual process for resending confirmation emails (see https://groups.io/g/GroupManagersForum/message/31063), or perhaps it may have been at one time. But I may have it all conflated with "Send Bounce Probe."

Regards,
Bruce


Suggestion for Section 8.14 Removed Member Notice

Mark Murphy
 

Add to Section 8.14 Removed Member Notice:

With a bulk removal, the Removed Member notice is not sent to the removed members.


Re: Additional Owners Manual Suggestions

Nina E
 

Thank you for the corrections and suggestions submitted in this topic. I incorporated them in the October 30/31 update. (The PDF is dated October 30 because that's when I submitted the updates to Mark; the HTML pages in the Help Center are dated October 31 because that's when Mark published them.)

- Nina


Re: Members Manual suggestion

Nina E
 

Thank you for the suggestion. I added a topic about searching for messages by number in the October 30/31 update. (The PDF is dated October 30 because that's when I made the updates and submitted them to Mark; the HTML pages in the Help Center are dated October 31 because that's when Mark published them.)

- Nina


Re: error in documentation

Nina E
 

Thank you for the corrections and suggestions submitted in this topic. I incorporated them in the October 30/31 update. (The PDF is dated October 30 because that's when I made the updates and submitted them to Mark; the HTML pages in the Help Center are dated October 31 because that's when Mark published them.)

- Nina


Re: Populating Display Name

Nina E
 

Thank you for your feedback, Bruce. I added a topic to the Owners Manual, under Managing members, about adding or updating display names. In the Members Manual, I beefed up the information about the Display Name field in Customizing your Groups.io account profile and individual group profiles (under Setting account preferences and viewing account information).

- Nina


Re: error in documentation

West Coast Compañeros Staff
 

We appreciate all your good work, Nina.

Robert

On 10/31/20 7:59 AM, Nina E wrote:
Thank you for the corrections and suggestions submitted in this topic. I incorporated them in the October 30/31 update. (The PDF is dated October 30 because that's when I made the updates and submitted them to Mark; the HTML pages in the Help Center are dated October 31 because that's when Mark published them.)

- Nina


--
MacBook Pro (Retina, 15-inch, Mid 2015)
macOS Catalina version 10.15.7
Firefox Version 77.0 / Google Chrome Version 85.0.4183.121


iPhone XR 64 GB
iOS 14.0.1


Members Manual suggestion

Duane
 

PDF October 30/31 2020

3.4.6
Should add a line about how to turn off 2FA.
"To disable two-factor authentication, click the Disable Two-Factor button, enter your Groups.io password in the popup box, and click Disable."
I'm sure my wording isn't quite correct since I don't use 2FA, but someone was having a problem understanding that it was the GIO password that went in the box.

Thanks,
Duane


Re: Suggestion for Section 8.14 Removed Member Notice

Nina E
 

Excellent suggestion – thank you! I added a note to that section in the November 6 update of the Owners Manual.

 

- Nina

 

From: docs@beta.groups.io <docs@beta.groups.io> On Behalf Of Mark Murphy
Sent: Saturday, October 31, 2020 9:48 AM
To: docs@beta.groups.io
Subject: [docs] Suggestion for Section 8.14 Removed Member Notice

 

Add to Section 8.14 Removed Member Notice:

With a bulk removal, the Removed Member notice is not sent to the removed members.


Re: Members Manual suggestion

Nina E
 

Thanks for the suggestion! I added information about disabling 2FA to the November 6 update of the Members Manual.

 

- Nina

 

From: docs@beta.groups.io <docs@beta.groups.io> On Behalf Of Duane
Sent: Monday, November 2, 2020 6:54 AM
To: docs@beta.groups.io
Subject: [docs] Members Manual suggestion

 

PDF October 30/31 2020

3.4.6
Should add a line about how to turn off 2FA.
"To disable two-factor authentication, click the Disable Two-Factor button, enter your Groups.io password in the popup box, and click Disable."
I'm sure my wording isn't quite correct since I don't use 2FA, but someone was having a problem understanding that it was the GIO password that went in the box.

Thanks,
Duane

161 - 180 of 383