I have developed a tool to be used by customers based on Google Sheets. The document contains a number of sheets/tab, half of which are for customer use and the other half protected and only to be accessed by the owner.
The protected tabs contain sensitive information from a central database and shouldn't be viewed by anyone else other than the sheet owner (me).
It seems that protecting these sheets has been working as intended until one customer noticed today that if he clicks the Version History, it displays all changes made and opens all the protected sheets!! This seems like quite a major loophole to the sheet protection feature...
Does anyone know how to turn off Version History so link just right of 'Help' in the task bar doesn't appear at all?
I found this, but that doesn't seem to make any difference. In the 'Turn off view history for one file' instructions, I don't have 'Tools > Activity dashboard privacy' And for the 'Turn off view history for all file' instructions, it doesn't remove the version history links right of 'Help' so customers can still access the history and therefore the protected files.
If someone can advise here, that would be appreciated.
You can NOT.
Not unless you have a work or school account as clarified in your mentioned link
Some Docs features are only available for work or school accounts, and
you’re signed in to a personal account: xxxxxx#gmail.com.
To sign in to your work or school account, click here.
Also further down:
If you don’t see Activity dashboard or the privacy settings:
If the file isn’t owned by a Google Account through work or school, no
one can see the view history. You haven't viewed a shared file owned
by a work or school organization. You may be signed in to the wrong
account. You’re signed in to your personal account: xxxxxx#gmail.com.
Related
I have a Google spreadsheet comprising of several worksheets and I am trying to publish the worksheets individually on separate webpages, preferably using embed. This is to provide access to users within a Google Workspace domain. The first published worksheet works fine and is duly visible to users allowed to view the Google Sites webpage. Subsequent worksheets are also published successfully but the previously published worksheets are no longer accessible. I get the following message:
"*You need permission to access this published document.
You are signed in as #.org.uk, but you don't have permission to access this published document. You may need to sign in as a different user. "
The above email address is an editor of the spreadsheet as well as being able to edit/view the Google Sites. I have tried everything by only using Incognito windows only, logging out of all accounts, checked settings, etc: I am always unable to publish more than one worksheet from the same spreadsheet at a time.
What am I doing wrong???
PS-1:
Following iansedan suggestion I have anonymised and simplified the spreadsheet. There are 2 tabs I want to publish to web: Group T and Group S.
I publish Group T to the web: works as expected in the browser (Chrome).
I publish Group S to the web and view it in another tab in the browser (Chrome)
It duly shows the published version of Group S but when I click on the other tab (to view the Group T which was OK before) I get the following message:
"You need permission to access this published document.
You are signed in as [my workspace email address], but you don't have permission to access this published document. You may need to sign in as a different user."
This is the link to the spreadsheet. I'm afraid I don't know how to share this better, the only way I could find is if you try to access the spreadsheet I will get a notification and will add your email address so you can view/edit it.
PS-2 Additional info
The respective links for the published are as follows:
Group T This one comes up with the "You need permission to access this published document." message
Group S This one shows the published worksheet correctly (as it was the last published!).
It looks like a caching mechanism somewhere is causing the issue but I have no idea where and how to prevent it! I've cleared the cache in the browser...
To publish individual sheets of a spreadsheet, use the Published Content and Settings button instead of the Publish button.
Uncheck the All Document checkbox and select the Group T and Group S sheets. After that click Escape and Start Publishing.
I had the same problem.
What youre doing is pausing one publication to start another one. Then, the first one is canceled.
Basically, there are two fields on the web publishing tab: one above another.
On the upper one, you chosse wich part of your sheet you will publish. That is, here if Jonh need to see "X", you select "X" and take note of the link to send to John.
On the lower one, you confirm all parts of the sheet that are being published at til that time. In other words, there will be more than one part in this fild. That is, if you havd alredy done the process to John (X), Anna (Y) and Floyd (Z), you will visualize X, Y and Z
Got it?
I am a BI administrator and author on my OBIEE (12.2.1.3.0). I need to create an analytics on users' browsing history. And then share it to their manager who is just another normal user himself (not an administrator). So I searched on Google for a solution. but, I didn't find anything other than "Manage Sessions" section in administration. However, that just shows online sessions, but I need the report per user and their last login time and browsing information. Besides, I don't want to give the manager administration privilege to access this section. instead, I want to create an analytics for him. but for analytics I need a relevant "Subject Area". I don't know if there is a table in OBIEE repository where I can query from. or generally, I might be thinking incorrectly and there are other ways to handle this kind of requirement. Any idea?
Actually yes, it is possible. As you may know, OBIEE repository tables, which can be used to show to end users as subject area that this is usgae tracking utility, just track information around sent queries to BI server and not more about users specifically.
In this occasion, you can use a method which called enhanced usage tracking for OBIEE that is presented completely here:
https://www.rittmanmead.com/blog/2016/12/enhanced-usage-tracking-for-obiee-now-available-as-open-source/
This is exactly what you want. All detail information about users activities in OBIEE and enve some redundant ones. You can create a physical table, then add it to repository file and display as subject area to end user with any permission.
Of course, according to your software environment or implementation structure, you are supposed to make some changes in this manner.
I hope this goes well.
We're having some serious issues with the mfbclient.exe tool that is part of the feedback platform of VSTS. Basically, our stakeholder's uploads are not being sent.
This is extremely frustrating as you can imagine, as the ability to take screenshots etc is a major benefit of using the tool.
Members of the development team who have VS2017 installed on their machines as well as the feedback tool, can access the feedback request via the email that is automatically sent out when you click on "Request Feedback". Everything works perfectly.
If we send the request to a stakeholder, they can click on the link and it opens up the tool correctly, they can step through the items and make notes etc., and when they submit, their responses come through into VSTS. However, none of their attachments come through. They all say '(Uploading) filename.png' in VSTS.
Upon looking at one of the stakeholder's machines, I can see the mfbclient.exe tray icon says '0MB of 10MB transferred'. Restarting the machine doesn't change this - the attachments don't get uploaded.
Upon further investigation, under %localappdata%\microsoft\team foundation\x.0\testmanagement\ i can see an XML file which contains the list of all the screenshots / attachments etc that are to be loaded. The screenshot files themselves also exist (so, the files aren't missing/deleted). For some reason, the files just aren't uploading.
If I remove the XML file, it clears the attachment 'queue', but as soon as more feedback is entered and a screenshot added, the same issue occurs.
I noticed there was an mfbclient.exe.config file, which I edited on one of the stakeholder's machines and changed the trace level to '4' (verbose), which I thought would shed some light on the issue. However, I can't see anywhere that the logs might be. Does anyone know?
I have tested this with the stakeholder being part of the exact same security group as myself and the team (as I thought perhaps it was a permissions error), but this doesn't change the behaviour.
The only real differences I can think of between myself and team, and the people who are having the issues (and there are quite a few users who have the same issue so it's not just 1 person's problem), is that these people are stakeholders rather than subscribers (shouldn't make a difference), and they don't have Visual Studio installed on their machines (also, shouldn't make a difference).
Can anyone please shed any light on this issue? Has anyone else had the problem? Can someone from MSFT help?
Just as Sebastian mentioned, the solution is changing the Access Level from Stakeholder to Basic.
Basic provides access to most features, except for Test and other premium features. Stakeholder access to those users who need to
enter bugs, view backlogs, boards, charts, and dashboards, but who
don't have a TFS CAL. See About access levels for details.
Basic provides most features, Stakeholders can use the Feedback Client since TFS 2013 Update#5 based on this user voice. Can't attach pictures seems a permission limitation for Stakeholders.
Whatever seems it's by design or a feature missed or an issue on current version of TFS and VSTS based on the Stakeholders license limitation. However the requirement make sense and I have submitted a new user voice here to suggest the feature, you can go and vote it up to achieve that in future.
UPDATE:
I agree with your point of view, it's more inclined to be a bug. And you have submittetd a feedback here: Feeback Client - Upload fails for Stakeholder
Whether user voice or bug, development team will take care of them. So, let's wait for the response. And for now, you can change to the Basic Level to upload the pictures.
I have the same problem with our VSTS.
The problem really is because of the Stakeholder-License.
If I submit a feeback with a stakeholder account the upload stays at 0%. When I change the user then to Basic in VSTS, the upload starts automatically and completes.
EDIT: this issue has been fixed, as per this forum post: Feedback Client - Upload fails for Stakeholder
I have been given a requirement to allow our sales team to view all of the issues that we are in the process of investigating/fixing that their customers are experiencing.
We've added a custom column that contains a list of all of our customers so that we can filter by customer.
We are going to add viewer accounts for everyone on our sales team.
On every issue we were going to add the relevant sales guy as a viewer. That way the sales guy will get an email whenever a customer's issue is resolved, moved to feedback, etc.
Here is the question:
We want the sales guy to be able to log into Mantis and on his "View Issues" page have a filter already setup that displays all of the issues he is monitoring, and only his issues (to avoid confusion). Is that possible?
We don't really care if he can see all of the resolved issues, unassigned issues, recently modified, etc on the "my view" page. This isn't really a security thing, it is a usability thing. I want to be able to send a link to the sales guy and tell him to bookmark it and it will contain a continually updating list of the issues that pertain to him.
This may be a workable solution, but it is still a little clunky.
If I send out a URL like this:
<SERVER ADDRESS>/print_all_bug_page.php?filter=<XX>
Where the XX is the corresponds to the value of "myself" on the monitored by box. For me it is 52, not sure if that will change as I play with the columns.
Therefore the link right now is:
<SERVER ADDRESS>print_all_bug_page.php?filter=52
What's clunky is: If the user clicks any of the column headings on this page for sorting the query string isn't included in the new URL and all of the issues are then displayed again.
Reading online material (e.g. Fowler, Gerard), it seems that Specification By Example stories should not be complete specifications of functionality.
Question 1: How does one starting off with SBE's decide how comprehensive their stories need to be in terms of describing all of the functionality of a system? I.e. when can I stop writing stories because I have captured enough?
Question 2: In an organisation where test teams verify products against the product documentation, if the stores are not a complete specification, am I correct in thinking that 'other' product documentation needs to contain all the cases that are not covered by the SBE's?
Regarding question 1:
The most important part of developing any system is that the development team has a conversation with the product owner. First find out the crux of the feature which they require. I'll answer this question by working through an example; let us say that the product owner may want a facility to login to their new website. This requirement could be written as:
In order to gain access to the website's facilities
As a user
I want to be able to login to the website
(Note that I'm using the Gherkin domain specific language for writing the scenarios and features in this answer)
With the product owner's key requirement specified, you should now discuss with them how you think this feature should be implemeneted from a users perspective (keep it high-level, don't use technical jargon, discuss with the business to find out what they want). So the first "happy path" scenario you might identify could be:
Given a user is on the login screen
When they submit valid login credentials
Then they gain access to the main website
After further discussion with the product owner they tell you that as the website contains extremely sensitive information, and that any failed log-in attempts should be reported to a system administrator. This would result in another scenario:
Given a user is on the login screen
When they submit invalid login credentials
Then the system administrator is informed of the failed log-in attempt
And the user is informed that their login attempt failed
At this point the product owner might say that these are the only scenarios they want for logging into the system. So from the development teams perspective no more investigation would need to be done regarding this feature (so you wouldn't need to write any more user stories). Sure, at a later point in the projects development, the product owner might also tell you that they'd like to inform a user when they last logged into their site before reaching the main website, but you'd only need to worry about this when they ask for it.
Regarding question 2:
The organisation should be verifying the products against "living" documentation e.g. using Cucumber(for example) which generates tests from the scenarios detailed above.
Also as I said in the answer to question 1, you should identify "just enough" of the scenarios/use cases to satisfy the product owner. What the product owner asks for is the complete specification. Don't try and second guess what the product owner might want because this may result in be a classic case of YAGNI.