I also went to the parent group, "Ministries," checked the permissions, and copied those to the descendants. Same problem. I'm really stymied now. Everything I was told to do made sense in that it *should have* fixed the problem -- but it has not!

Two things.

1. If the permissions seem okay, then you may need to flush the site's cache.  I go so far as to recycle the ASP instance and restart the entire IIS server.

2. If 1 doesn't change anything, then the site is probably hopelessly unstable.  From here, I've deleted all site pages, then made sure the database didn't have any ghost tabs left over and gotten the site to work.  Other times, this did nothing and I had to start from scratch.

DNN is very popular and yet a huge amount of trouble in some cases.  None of the troublesome cases seem to have a discoverable explanation.  I stopped taking those customers as I was the next dev in a long line that could not get their DNN working well.