[thetwistedpanda]

It doesn't exactly work that way, although that may change in the future if I can find a logical way to do it.
When banning via sm_ban, the plugin only takes into consideration the upper/lower bounds for the space between two points. What I mean by that is if you ban for 7 minutes, the plugin wants to find the lower and upper bounds for that 7 minutes, so it'll choose "5" and "15" if you're using the default configuration. Since it has the upper bounds, it's just going to check permission for that one and see if you have it. If it fails, it'll consider going through the lower bounds and beyond if you have the reduce option enabled. "5" and "15" is considered a separate entry while "30" and "60" would be considered one. The plugin doesn't care about the higher entries once it finds the upper/lower bounds.

Now if you're banning via the ban menu in a modified basebans or sourcebans, the plugin is simply going to loop through all of the entries and see if you have permission for them. That means if you have the "b" flag, assign players with "b" access to "5", "15", "30", "10080", and "0", they'll have the ability to mute for 5/15/30 minutes, 1 week, or permanently.