开云体育

I want to try out the Slack member integration mentioned in the features section but I am not seeing any how-tos. I don't see it mentioned specifically under the paid features.

I go here:?

Go to Sync'd with Slack team

And? when I click it gives me an OAUTH error message.?

I am stuck on what to do next.

i have the same problem.? any suggestions out there?

What, exactly, is the deal with Slack Member Sync. Like Jeff, I was tempted to change over to groups.io exactly because of this advertised feature. But there is zero help anywhere on how to do this. I even pinged tech support and got crickets chirping for 3 days now.

On Tue, May 22, 2018 at 11:39 am, Dale Visser wrote:

What, exactly, is the deal with Slack Member Sync.

<chirp>? ?<chirp>? ...I don't think it works...? ?<chirp>? ?<chirp>

Bruce?
--
The system Help is your friend.??/static/help

At this time, it appears as though the advertised feature to sync between a Slack group membership list a groups.io membership list is not implemented or supported.? If this is wrong, please reply.

?

For the UNB Amateur Radio Club, I have groups named unbamateurradioclub in both systems.? I expect that these lists will evolve differently and have different uses as groups.io posts are archived indefinitely and for unpaid Slack groups only the most recent ten thousand messages maybe searched.

The last mention I can find of any problems with Slack was late February last year, .? It was working in late January of this year, /g/GroupManagersForum/topic/9586833.

Duane
--
Help: /static/help
GMF's Wiki: /g/GroupManagersForum/wiki
Search button at the top of Messages list
A few site FAQs: /static/pricing#frequently-asked-questions

On Tue, Sep 4, 2018 at 08:38 AM, Brent wrote:

At this time, it appears as though the advertised feature to sync between a Slack group membership list a groups.io membership list is not implemented or supported.? If this is wrong, please reply.

?

For the UNB Amateur Radio Club, I have groups named unbamateurradioclub in both systems.? I expect that these lists will evolve differently and have different uses as groups.io posts are archived indefinitely and for unpaid Slack groups only the most recent ten thousand messages maybe searched.

Brent,

It will be useful if you can document exactly what is not working. In other words, the steps you are taking and the results / error messages. In case no one on the GMF forum has direct experience with Slack integration,?this information will also be required to submit the issue to groups.io technical support (email: support AT groups DOT io)
?
--
Gerald

Gerald:

Duane:

Sorry. ? I did not initially see your post. ?I have just started using both groups.io and Slack. ?
In groups.io, settings, member sync, I just set up member sync between the two groups called unbamateurradioclub. ?I am the owner of both groups. ?i had to authenticate with Slack. ?At the moment it seems to work. ?Thank you.

Best regards,

Brent

I have been getting that same OAUTH error message when I try to sync with Slack.? I have a clue as to what is wrong though, and was wondering if someone could confirm my theory.??

I was testing this on a new group that had no messages and at first I got that same message, then the sync seemed to be approved by Slack? ?On looking at it though, I realized I had synced the correct Slack group with the wrong Groups.io group (I have three).? ?I deleted that and then went to the correct Groups.io group - which has a subgroup - but no matter what I can't get it to reauthorize.? ?I know that when you add a subgroup it changes the url for the group so was thinking that might be the problem.? ?The first group I tested it with had no subgroups.?

So easy fix right - the group has no members so just delete the subgroup and try again? ?I was about to do that but read that when you delete a subgroup, the name of that subgroup becomes unavailable for later use.? ?Then I read someone say that if you rename a subgroup before you delete it, this won't happen - but that was never verified.?

Before I go deeper down the rabbit hole could someone let me know if I am on the right track.? First, is the Slack integration generally working for people here?, second is my theory about the authentication problem being related to subgroups plausible? and third, if so, will that renaming trick work before I delete the subgroup?? ?It is a common name and I would hate to lose it.?

Thank you

On Sat, Dec 15, 2018 at 09:25 PM, Rob Gordon wrote:

I have been getting that same OAUTH error message when I try to sync with Slack.?

Rob --

Not many people here have much experience with the Slack integration, as a quick search of the GMF archive will show. You might want to check the following thread in the beta group regarding Slack integration and subgroups:??.?

Hope this helps,
Bruce?
--
The system Help is your friend.??/static/help

Rob,

I was about to do that but read that when you delete a subgroup, the
name of that subgroup becomes unavailable for later use.

I don't think that's true of subgroups, only primary groups.

That is, in the form: "[email protected]"; or the alias form "[email protected]" (which is also the form used by groups which have no subgroups) only the "primary-name" is required to be unique system-wide and is reserved on deletion.

Then I read someone say that if you rename a subgroup before you
delete it, this won't happen - but that was never verified.

Again, I think this only applies to primary group names. When you rename a group the prior name is not held in reserve.

I've never used Slack so I can't help with the rest of your question.

Shal


--
Help: /static/help
More Help: /g/GroupManagersForum/wiki
Even More Help: Search button at the top of Messages list

On 12/15/2018 19:08, Shal Farley wrote:

I've never used Slack so I can't help with the rest of your question.

Shal

Just to say, as someone who does use Slack and has coded an OAUTH integration at work, that this is not a Slack issue, it is an OAUTH protocol issue. There is likely a bug (hard to say what from here) in the token exchange and groups.io is not receiving/recognizing/validating/etc. a token properly.

There's nothing anyone on this list can do about this, the ball is entirely in Mark's court and the previous suggestions of writing to the support email address is the only viable route forward.

Best,

Glenn