We are pleased to present below all posts tagged with 'Security'. If you still can't find what you are looking for, try using the search box.
Have you created a document or file recently that you want to share with limited access to others? Sharepoint "View-Only" permissions have caused some confusion when it comes to file sharing. Find out why the "View-Only" permission doesn't do what you think and how to properly secure your documents by preventing them from being downloaded.
Sometimes saying "yes" to make your CRM users happy can create unnecessary complexity that chips away at the user experience and, ultimately, hurts adoptin. In this article we'll look at some helpful questions to ask before adding a new field to CRM.
When you work with SharePoint permissions, you quickly figure out that you want to touch them as little as possible. With a lot of things in SharePoint, permissions inherit top down. So this means that it’s a best practice to always use that inheritance as much as possible. But in today's post, I'll show you how to use PowerShell to change those permissions for all libraries, folders and files in the site!
In today's post featuring PowerShell, I'm going to show you how to use a script with a few functions and some handy tricks to quickly reset permissions with multiple libraries, folders and files. This can be very difficult to handle manually, especially when there are many many libraries with many folders and files with broken permissions.
A client recently found he could not enable a user he needed to use in one of our sandbox organizations. Every time he tried, he got “The user ID associated with the current record is not valid”. This blog explores the fix.
There’s more to the concept of Team Ownership in Microsoft Dynamics CRM than you may originally think, which means you’ll want to give that topic significant consideration and understanding before embarking on a security model that utilizes team permissions or team ownership. In releases prior to 2011, the concept of Teams existed but Teams were simply groupings of users. Since version 2011, a Team can actually own its own records, and can have its own security role(s), giving CRM architects more options for building more complex security schemes. Let's talk about these options now!
If you’re still using Microsoft Dynamics CRM 2011, now is the time to consider an upgrade. With CRM 2015, you can teach your CRM to do all sorts of new tricks that will make your team more productive. In this article we will look at the new administrative features that you can use to expand what your team can do with CRM. Don’t worry, we’re not going to get too technical.
Concerned about how to protect your customers and the data in your CRM system? So are many business executives. But you may find some surprises in the 5 keys to protecting one of your most valuable assets.
Earlier this week it was announced than an international hacker had successfully made off with over 3 million social security numbers and almost 400,000 credit and debit card numbers from the state of South Carolina. State and local governments have collectively spent billions of dollars trying to secure their data systems. In spite of this investment, a hacker was able to identify and exploit a weak spot in their armor. As public sector budgets are continuing to shrink, there is pressure to add more software applications to automate tasks and lower costs; increasing pressure to cut costs on security for these applications; and increasing pressure to extend the life of less secure and aging legacy computer applications. The result is that our government agencies are at increasing risk of successful cyber-terrorism through a greater number of applications, lower security standards, and aging applications that should be replaced.
How could South Carolina and other state and local governments cost-effectively protect vital citizen, business and government records? The answer comes from an emerging private-sector technology: cloud computing.
If you’ve been dabbling in SharePoint 2010's new hosting (multi-tenant) environment and been creating host-named site collections, you have may noticed that the default SharePoint security groups typically created by default are not there in the root web. These include:
These are created by the SharePoint API, and apparently isn’t called properly when host-named site collections are created through PowerShell in a multi-tenant environment. This ONLY happens in a multi-tenant environment. Even if you create the host-named site collections through PowerShell in a non-hosted environment, the first time you visit the site, you might be prompted to choose the site template and to create the default security groups.
So how do we get them back without creating them manually? Read on...
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.