There IS a permission group called "regular users", everyone not added to another primary group will belong to this group.
On top of that, there's post count groups. You do not need to manually add anyone in a group, to alter everyone's permissions.
Yes, but when I converted over, it moved my users in to groups that phpbb calls ranks. I need to move a large number of those users in to the user group.
there is no "automated" way to do it directly.
As you know, you can add users individually in their profile or in bunches in the group settings page.... but that does involve manual effort.
The next way would be to directly add them in the database...
1- set up the new group and note the ID of the group (in the example below, the groupID is 44)
2- Assemble a list of User IDs of the users which you want to put in this group (make a comma separated list - in the example below, the three I am users are 21,22,23,24,25)
3- if this group is to be their PRIMARY group (and note that a user in SMF can only have **ONE** primary group) then
SET @id = '21,22,23,24,25';
UPDATE smf_members
SET id_group=44
WHERE FIND_IN_SET(id_member,@id);;
4- if this group is to be a SECONDARY group
(and note, by default secondary groups are not displayed in the user's post-data mini-profile)
(also note, permissions in SMF are PERMISSIVE and INCLUSIVE -- this means that a user has ALL permissions ALLOWED by *ANY* group they are in - the only way to overset this is to turn on and use DENY (which makes that specific permission EXCLUSIVE)
(also, also note, that this assumes that the user does NOT have anything set for secondary groups yet.... )
SET @id = '21,22,23,24,25';
UPDATE smf_members
SET additional_groups=44
WHERE FIND_IN_SET(id_member,@id);;
(If *ALL* of the target users already HAVE secondary groups... )
SET @id = '21,22,23,24,25';
UPDATE smf_members
SET additional_groups = CONCAT(additional_groups , ',44')
WHERE FIND_IN_SET(id_member,@id);;
(If you have secondary groups already set for some but not all, it becomes more complicated)
As always, BACKUP before doing anything.
I have not tested this, but I believe the code above to be correct as it is similar to things I have done in my DB in the past.